Maybe the true Everett was the cherry picking we did along the way.

A zoo used to be little more than animals in cages put on display for public viewing. The idea is a modernization of the menageries that used to be kept by nobility, and the first public zoos were just these menageries opened to the public:

Until the early 19th century, the function of the zoo was often to symbolize royal power, like King Louis XIV’s menagerie at Versailles. Major cities in Europe set up zoos in the 19th century, usually using London and Paris as models. The transition was made from princely menageries designed to entertain high society with strange novelties into public zoological gardens. (ref)

People who post these are being very selective. Some of them hold up, some of them not so much. Here’s a book:

The Outbursts of Everett True (1907)

Page 42 and 100 are good examples.

Minecraft?

Hard to do better than the OG endless sandbox.

Um, if it’s “parallel” (e.g. separate from the OS package manager) then it’s not centrally managed. The OS package manager is the central management.

There might be specific use cases where this makes sense, but frankly if segregating an app from the OS is a requirement then it should be fully containerized with something like Docker, or run in an independent VM.

If a flatpack is made reasonably, then it gets library updates independent of the app developer doing it.

That feels like a load-bearing “if”. I never have to worry about this with the package manager.

Oh no, no GUI nonsense. Single, simple shell command update for the whole system so that it can be properly remotely managed, please. Something equivalent to sudo apt upgrade

This is true, the only shared libraries are usually the .NET versions, but so many apps depend on specific .NET versions that frequently the modularity doesn’t matter.

Can I sudo apt upgrade my installed flatpak apps?

Metronet will be supplying an Optical Network Terminal, probably like this one:

This is basically the equivalent of a modem for cable networks. It does not provide routing functions. You’re probably stuck with the ONT they supply, but it shouldn’t matter much, definitely not for anything internal.

It looks like Metronet normally supplies Eero WiFi mesh devices for home networking - are the ones you currently have supplied by Metronet? They might just replace the modem with the ONT and leave the existing Eero gear, or they might upgrade the Eero gear to support the higher speed available on the fiber network.

In any case, if you are using ISP-supplied network devices then you don’t control the router, which means you can’t set up things like port forwarding to access your home network from outside, or configure VLANs to segregate devices on your network, or control things like DHCP.

Technically there’s no reason you have to use the Eero devices from Metronet, you should be able to plug any router into the ONT WAN port and have internet service. If you don’t want to get too deep into network config, then any modern consumer WiFi router will work (but not a modem/router AIO device). If you want to have a bit more control, look for one that supports OpenWRT.

Same as it ever was…

If you’re separating your application from the core system package manager and shared libraries, there had better be a good and specific reason for it (e.g. the app needs to be containerized for stability/security/weird dependency). If an app can’t be centrally managed I don’t want it on my system, with grudging exceptions.

Chocolatey has even made this possible in Windows, and lately for my Windows environments if I can’t install an application through chocolatey then I’ll try to find an alternative that I can. Package managers are absolutely superior to independent application installs.

Asceticism is a dead end.

The Internet is a fantastic example of building the airplane while you’re flying it. We can’t just put this thing on the ground and rebuild the engine, we’re in flight and there’s a lot riding on it.

IPv4 was drafted in 1981 and adopted by ARPANET in 1983. For all practical purposes, there was no “internet” yet - which is to say that IPv4 predates the Internet.

IPv6 was drafted in 1998, but wasn’t adopted as an official standard until 2017. The Internet had grown exponentionally long before any manufacturers were even considering implementing IPv6.

There is a mountain of telecom infrastructure built over the past 40 years that still has legacy hardware bits scattered through it. There is a jungle of interdependency tangled through firmware and low-level software that no one living has any real understanding of. There is an ocean of application software that was built on assumptions about the underlying infrastructure that no one ever planned to be updatable, and the creators are long retired.

Anyone want to take bets on how many pieces of slapdash web software out there use some hard-coded regex to pick IPv4 addresses out of strings? Good luck getting those things updated. IPv4 is going to be with us for a long time in the form of shared libraries, Nth-tier dependencies, and legacy hardware drivers.

“In theory, theory and practice are the same. But in practice…”

the tyranny of the default strikes again

“Extreme” pride in any country is just nationalism. If we have less of that, then we have gained as a society.

*Edit: Which is not to say that you should take no pride in your home at all. A lack of pride is similarly unhealthy, it leaves you uninvested in the place where you (and probably your friends and family) live. Even if you don’t approve of your current government, I guarantee you there are things to be proud of in your home, and you should take pride in them and work to maintain and improve them.

to meet the demands of our new machine overlord dunsel

or… you end up with more smaller files to keep track of in order to carry the same information that could’ve been in one large file

Upvotes are for visibility.

It’s related. Warming ocean temperatures are amplifying the hurricanes and destabilizing currents like the Gulf Stream - both symptoms of the same problem.