There is nothing to it. I once made web.py-server that combines maps from two countries. While kayaking. It was too annoying when you had to switch programs to see what is on other side of river. Unfortunately they do follow Google tiles standard anymore.
I will use C and C++ only, Python too slow, Rust ( I despise the community), JS is poorly designed bloated mess, Java way too verbose, Swift is for Apple only which is limiting, I wanted to use objC but I heard Apple is gonna dump it soon.
C and C++ is the only viable languages here since this project is all about graphics.
I saw PDP-8 and two ASR-33 on a garbage pile in around 1980. I knew that if I take them, it will destroy my life, I would do nothing else than tinker those for the rest of the millennium.
That’s why, when the local college was decommissioning their IBM minicomputer, I opted not to buy it (it would have been under a thousand bucks, as I recall, although I probably would have spent that much a month on air conditioning if I set it up in my apartment, not to mention the overall impracticality of it.
If you think the 6502 doesn't have enough registers and addressing modes... Try the PDP-8.
The PDP-11 on the other hand has a lot of registers and addressing modes. A kid with a TRS-80 in 1980 might have thought the "16-bit" PDP-11 looked like the future although it really was the past, as it dated from 1970. The greatest weakness of it was that the user had a 16-bit address space so a PDP-11 running RSTS/E gave everybody a BASIC experience a little bit better than an Apple ][ or alternately the ability to run applications similar to CP/M. The machine as a whole had more than 64k of RAM but as a user you got 64k of code and 64k of data -- so it was a little bit better than the 8-bitters of 1980 but not as good as the IBM PC for having a bigger "problem space" to work on bigger problems.
My high school got a VAX to replace our PDP-8 and the computer club got it. We had two video terminals and a printing terminal, originally the printing terminal was the main terminal that was used when the machine was brought up in single-user mode. I swapped in one of the video terminals in this role, powered it up, and had the VDT catch on fire -- so we cleaned up the other terminal before bringing the machine up with that.
When I started doing BBSs, I used 300 baud at times. Unbearable. "Nobody ought to need more than 2400 baud" is what I felt with the upgrade! Until 14400 came along, of course...
It got really bad when the BBS got all fancy and colorful with the ANSI graphics. Every character displayed might require 6 or 7 bytes down the wire to change the foreground and background color so your 2400 baud modem acted like a 300 baud modem or worse.
Small numbers are "eq" in python. It saves space and time, because probably those numbers dont even exist, and the value is derived from the pointer value.
>>> a=3
>>> b=3
>>> a is b
True
>>> a=1e20
>>> b=1e20
>>> a is b
False
But in Commonlisp all numbers are "eq". Very strange. Is there heap of numbers and once created, they reuse those?
[4]> (setq b 1E20)
1.0E20
[5]> (setq a 1E20)
1.0E20
[6]> (eq a b)
T
In Common Lisp, in fact, no numbers are required to be eq! Even (eq 0 0) is not required by ANSI CL to return true.
Why your Lisp implementation produces true for (eq a b) is probably because of the following.
Firstly, in Common Lisp there are single and double precision floats. Floating point tokens written with E or e are single. An implementation is allowed to map that to a 32 bit float. If the implementation has 64 bit values, it can easily arrange for single precision floats to be unboxed without any special tricks; they need only half the word. Try evaluating with 1D+20 to see what that does.
But even 64 bit values can be unboxed with a trick called NAN tagging.
I implemented NAN tagging in TXR Lisp (which has only double-precision floats), enabled on 64 bit targets:
64 bit machine:
1> (eq 1E20 1E20)
t
2> (sizeof val)
8
32 bit machine:
1> (eq 1E20 1E20)
nil
2> (sizeof val)
4
On 32 bits, floating-point objects are on the heap.
It's pretty important to have unboxed floats for intense numerical work.
It's not guaranteed that eq will return true for two numbers of the same value in Common Lisp. It happens to work much of the time, but it is never guaranteed to work. For a given implementation it could even be true all the time (as it's not disallowed), but for portability it should not be relied upon.
This is the most important issue, especially in EU:
"If a kite weighs less than 25 kg and is tethered without a propulsion system, it is not subject to the EU UAS Regulation. This means that, unlike drones, such kites are exempt from registration and licensing requirements, regardless of whether they have a camera."
Please shutup. Last time this kind of EU-whining produced only "If you dont accept cookies, you can piss off"-type checkboxes, whose effect to security is less than zero.
The Cookie Law is different to the GDPR, I don't understand how HN of all places keep getting this wrong after 9+ years of GDPR, it's just a meme and I wish people here would be more well informed.
From the perspective of many non-EU citizens, it's just one more piece of EU legislation that hurts and annoys. Being technically part of the GDPR or not isn't terribly relevant for most people.
Note: I'm not defending or criticizing the law, just talking about how many people perceive it outside the EU.
Vitamin D is fat soluble, so overdosing is very possible. 4000 IU (100 µg) is the average tolerable upper limit (UL). I'd get checked for kidney stones too, which are possible with Vitamin D, calcium, and Vitamin C overdoses.
At unmitigated baseline, I'd be chronically Vitamin A, iron, and B-12 deprived. I have to take more than the UL of each, but the amounts are periodically recalibrated by blood tests. I have ginormous kidney stones that will eventually need to be removed.
I havent even seen a doctor about this. I was complaining to ChatGPT about occasional dizzy spells. It found out some half a dozen other symptoms and the fact I was doing 100µg D made the diagnosis obvious.
-- It worked like a charm, in few days all symptoms were gone.
Uh? You shouldn't be taking medical advice from a bot that hallucinates without an ability to fact check its own answers. Get a blood test if you are concerned.
It gave them an idea with a simple way to try it out, the person did that, and the problem went away. Nothing wrong with that. A random article on the internet would have been no different in this case.
I am not concerned. Unlike America we can't get blood tests without doctors orders. Last time I did it it was like €200 and basically useless, because it was just iron deficiency, which old-time doctors diagnosed from color of membrane around the eyes.
When taking "a lot" of Vitamin D, one should also take an adequate amount of Vitamin K2 and Magnesium. They work synergistically and will prevent leaching of calcium into the bloodstream.
Originally this program was running on Python For Symbian, which is historic and funny. https://github.com/timonoko/webpy_map_server
Tiles.py seems to be how you decode other systems to the Google-tile system.
reply