That was equally true for previous generations, and all those generations had exceptions -- kids that were excited about it, despite the other kids not being interested. (I figure the majority of Slashdot may have been such exceptions.)

Do we have reason to suspect the current generation is a unique special case, the one generation where somehow all of them make an effort to never learn about computers?

I bet some of them are like some of us, a 2026 minority that we would have recognized 40 years ago.

I've never seen generators on cell towers, and the batteries last a few hours. They're meant to cover the occasional western world power outage, not a major one.

Yepp, one of the reasons being that POTS will work even during power outages, as long as the central switches are powered. Your VoIP will be down if your house has no power. It probably is more efficient, but that "saving" is also simply shifting some of the power usage to consumers.

The market is a wet dream of manufacturers, of course. Already knowing that for all the forseable future however much you can produce will be sold at very good prices - amazing.

Until the house of cards comes down. Most of the stuff ordered is, as someone put well into a meme, money that doesn't yet exist buying chips that don't yet exist for data centers that have not yet been built.

That is highly speculative.

And if that works, then I think the days of pi being irrational will soon be over.

In which alternate reality?

Iran is not "a", but "the" supporter and financier behind Hamas, Hezbollah, Houthis and a bunch of other militias and trouble sources in the region. So no, they were absolutely not playing nice, even if you ignore all the atrocities inside Iran.

Yes, but Trump's will go in 3 years by itself. The IRGC regime will not.

We had a vote on that. Your proposal lost. Deal with it.

"Jailbreak" definitely implied something illicit in 1974 when AC/DC performed the song, but in 2026?! No. Jailbreaking is totally legit 99 times out of a hundred.

Jails were once respected because they were a product of society's consensus. When DRM appeared, jails became anyone's restrictions, with no societal inputs and no claims to legitimacy.

If you break out of the county jail or federal prison, that's a whole other thing than breaking out of your neighbor's sex dungeon. And almost all the time we talk about "jailbreaking" now, it's analogous to the neighbor's sex dungeon. Nearly everyone would agree it's legit to leave, and any illicitness is on the part of the captor!

[I]t's important to note that jailbreaking a Kindle might violate Amazon's terms of service.

Isn't the context here, that there is no service? I suspect that whatever terms the two parties came to agree upon, Amazon is the one who has initiated the violation of those terms, by ceasing to provide service!

Slashdot is a website for the elderly.

Not just not accurate but wrong.

That's like saying the price of the battery in an electric car is that car's price minus the price of a comparable ICE car. No, it isn't. There are more differences than just the battery.

And yes, of course they recoup their development costs. But that doesn't mean that the OP is right in this context.

errr... Apple doesn't charge for its operating system. macOS literally doesn't have a price.

Do you really mean that if your git repo were corrupted, restoring a snapshot of the repo from backups wouldn't work? If that's true, then it sounds like your backup system is broken. The hashes after restoring ought to be identical to what they were before the backup.

If git used the files' iNode numbers for its hashes, then I could understand how a filesystem-based backup/restore might not really work; you'd have to backup at the block level instead. But git doesn't use the iNode numbers.

git isn't magical. It only knows files. It doesn't know if you moved the repo, copied the the repo, or restored the repo from a ten year old backup. I have moved git repos around plenty of times, `cp -a`ed directories with repos, tared and un-tared directories that contain repos, and the copies have always Just Worked without any hash mismatches.

mkdir ~/test. cd ~/test. git init, touch test.txt, git add test.txt and git commit. cp -a ~/test ~/test2. cd ~/test2 and check out the backup repo. The backup is valid. Then simulate a disaster with rm -rf ~/test. Then recover from the disaster with cp -a ~/test2 ~/test and you've just restored a repo from filesystem-level backup. The resulting repo works perfectly and its hashes aren't off. git has no idea you deleted and restored under its nose. Try it yourself.

What am I missing? I'm not surprised to be called idiotic, and the shoe often fits. But I'm surprised to be called that over this.