Yeah here in Finland the archive site seems to come and go on a monthly basis.

I suspect, for many, that implementing a forth is more interesting than using a forth.

Once you start writing really complex programs the system gets painful and hard. But trivial things are easy, and the consistency is so appealing.

It is the bootstrap that makes it interesting.

Creating the required primitives in Assembly, and then the remaining userspace out from them.

Afterwards it is programming like most languages.

I have done it with Lisps though.

Also on 8 bit home computers it provided the feeling to be coding close to Assembly while being close enough to BASIC as high level language.

  > I think you're the one who missed the point

Yes, I would like to know more ..

Ha, caught that reference. That brought back memories.

I'm doing my part!

Only oddity was the reference to the "router cache". I agree if your browser tried to lookup example.com the local cache would be used, but then it would be the system's configured DNS server - and that would most likely be an ISP, rather than your local router.

(Assuming a typical home connection, your router is _probably_ not a DNS server with local cache, it probably is a DHCP server which will hand out the upstream/ISPs' nameservers.)

I think this is probably quite dependent on what’s normal for ISPs in the region. In the UK for example, every ISP router I’ve had runs a DNS server and it’s that which is given out via DHCP. It then forwards onto the ISPs DNS platform.

In Scotland I was with Telewest, then Virgin, and my memory is always that the DHCP pushed out the external IP of the ISP's DNS servers.

Nowadays I'm in Finland and definitely the router runs no DNS service, the DHCP service advertises the ISP resolvers.

Probably depends on the region/ISP I guess, but I had no expectation that it would be the more common option.

American here, most of ISPs here do it as well. With modern router hardware, there is plenty of hardware available to run tiny DNS server that caches and forwards all requests to ISP upstream. Memory overhead is probably about 50MB and CPU overhead is trivial, probably .1% or less.

I would argue the contrary - most home routers are running a DNS server of some kind. They forward to upstream, but will resolve local names like your printer and whatnot.

dnsmasq is the defacto tool on these embedded devices for dhcp+dns. probably a billion deployments. it's up there with sqlite for most used tech.

IIRC a resolver is what people would think of as a DNS server only it's not an authority for any domains. Like you said, they're used to get load off of authoritative servers and are very common. I think dnsmasq is mentioned explicitly in the O'Reilly locust book but it's been a while.

My parents are with Bell (the biggest ISP in Canada) and use the Bell Gigahub (Router/AP/Switch in one). It does have a DNS cache and the its set as the DNS resolver in their DHCP configuration.

The system's configured DNS resolver is usually your router.

I wrote a console-based mail client, which was 25% C++ and 75% Lua for defining the UI and the processing.

It never got too popular, but I had users for a few years and I can honestly say MIME was the bane of my life for most of those years.

Indeed. A big chunk of my email parser deals with missing or incorrect content headers. Most of the rest attempts to sensibly interpret the infinite combinations of parts found in multipart (and single-part!) emails.

Microsoft didn't write Internet Explorer, they licensed it from Spyglass, they had a "Spyglass Mosaic browser" which was ultimately based on Mosaic.

Most of the "Awesome XXX" lists are designed solely to promote their creators pet project.

You can see the gaming happen early on in many of these lists, where commercial things start appearing quite highly, or weirdly the project get sponsored.

Once they get popular the creators abandon them and start ignoring the updates/PRs because their task of feeding traffic to their personal projects has been accomplished.

It was only a couple of years ago since I wrote an assembly language program of my own and got hit by branching-limits on the Z80 processor.

I did exactly the same things that were suggested in this article, either inverted conditionals, or had a thunk - essentially "jmp nextJump", where that jumped to the actual location.

I sometimes spent a few hours shuffling code around to remove the longer jumps and re-order code in groups closer together to save individual bytes.

Tesla-related fatalities probably count already, albeit without that label/name.

I think "for work" is very definitely the reason for me. I've run Linux at home since 1994 or so.

As a sysadmin/devops person 90% of my life is emacs, a browser, and collection of terminals. When I get a job I get offered a choice between a windows laptop or a macbook. Sometimes, rarely, I'm allowed Linux, but usually they say "compliance" or that their security scanning software won't support it.

So I use macbooks for work, but I wouldn't pay for one personally. But they allow me to run terraform, git, shells, and similar things in the way that I'm comfortable with.