I switched from a giant docker compose file to podman quadlets on my homelab. IIRC it look me a little while to translate the first couple of services because there wasn't (at the time, at least) as much documentation/examples of quadlets as compose files, but after that it was a piece of cake. I highly recommend them.
The only issue I have is validation, there isn't a convenient built-in command to validate quadlet files and systemd doesn't warn you if any fail to generate. You either have to do a --dry-run first (and probably alias the full command to something reasonable) or check the journal for errors.
I don't like my wife's car for several reasons, but one thing it absolutely nails is the dash: all the lights are orange. It's a night-and-day difference (pun intended) to most cars that have blue lights everywhere, plus an LCD screen in newer models.
It's been a few years since I went with Fastmail over Proton, but if I remember correctly Proton prioritizes privacy while Fastmail prioritizes other features which were higher up on my list, like storage (not as important to me now), custom domains, email aliases. Fastmail also gives you static webhosting, which I don't think Proton offers (could be wrong).
Seconded. Even if one unknown number call isn't a scam, they will almost certainly pass on your number to ones that are. I made the mistake of answering one last week and since then I've been absolutely drowned in spam calls. Some of them even call a second time immediately after the first attempt, presumably to try to break through DND.
> Sending HTTP requests is a basic capability in the modern world, the standard library should include a friendly, fully-featured, battle-tested, async-ready client.
I've noticed that many languages struggle with HTTP in the standard library, even if the rest of the stdlib is great. I think it's just difficult to strike the right balance between "easy to use" and "covers every use case", with most erring (justifiably) toward the latter.
> While it is theoretically possible that the relays could fail on through some sort of physical failure, this is so unlikely that we did not design for it.
Anecdotally, I've had a relay fail on when I inadvertently pulled more amps through it than it was rated for, so it's definitely possible.
Web development has certainly gotten more complicated, but that's mostly because people are doing more complicated things. Writing the equivalent of a "Geocities, Blogosphere, and StumbleUpon era" site doesn't have to be any more complicated than it was then. My email provider offers free static hosting; I can upload some HTML files and have a website running in about 10 seconds.
> Good tools don't hide complexity behind a curtain, they eliminate the need for it.
Good tools absolutely hide complexity behind a curtain. The faucet example at the beginning, that tool is hiding a whole industry's worth of complexity. The trade-off is that it only does one thing. If you want to do something more complicated e.g. build a water park, you either have to deal with that new complexity yourself or hope someone else builds the infrastructure you need.
I can sympathize with the author that the web isn't as easy to create on as they envision. That would be cool. But so would flying cars. Those aren't impossible either, but both require a whole lot of "plumbing" that hasn't been built.
I think that section left out some details. On my Unifi setup, the router's IPv6 connection is configured with DHCPv6 (SLAAC isn't even an option) while the local networks are configured with SLAAC.
My experience has been the opposite, especially since Rails has included more batteries over the years. You need fewer non-Rails-default dependencies than ever, and the upgrade process has gotten easier every major version.
My org (USA) was affected. I wasn't the primary person dealing with it, but from what I gather one user marked one of our emails as junk, and then suddenly all of our emails to Outlook users started getting blocked.
I really enjoy the original Earthsea books. I guess my expectations of sci-fi are different than magic/fantasy; technology feels like it should be explainable in a way that magic doesn't. I'd probably enjoy Bradbury more if I approached his stories as fairy tales rather than sci-fi.
> Bradbury’s stories are about people, deeply real and deeply feeling people. ... and less interested in exactly how the ray guns worked.
Maybe this is why I never really got Bradbury. When I read scifi, I can't help but consider the logic of the world that's being described, and Bradbury's worlds aren't really logical (e.g. who would live on such a strict timetable? wouldn't all the singing and rhyming be annoying? how is the house still being powered?). But it makes a lot more sense if the point is to convey feelings. Kind of like an impressionist painting I suppose.
The only issue I have is validation, there isn't a convenient built-in command to validate quadlet files and systemd doesn't warn you if any fail to generate. You either have to do a --dry-run first (and probably alias the full command to something reasonable) or check the journal for errors.