And subject that power generation to the exact same regulations, environmental and otherwise, as any other. Do that, and we won't be seeing many new datacenters for the next 20 years.

They don't need to build an electric vehicle factory for that. I hear Tesla has a metric crapload of Wankpanzer's available real cheap.

I needed a good laugh, but that is exactly the opposite of how it actually works. They will be a discounted bulk price, or they'll build somewhere that will. That discount will delay the building of any new generating capacity, because the utility doesn't have the income. And while they will reliably use power, big customers generally get - because again, if they don't, they'll go somewhere that will - generous payment terms (you have to pay within 30 days of receiving at statement, they may have months, or more), and often don't live up to those.

All of those fairly standard business practices are easier to arrange in third world countries. That's why they're building there, and not in the US.

..OpenAI's statement about Altman being "not consistently candid"
Sam Altman is bad at lying. I imagine the board caught him in half-truths or omissions. He's not a mature enough liar to be a CEO. Nadella is though.

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.

My router's hardware's parts were made in China. Its software was made as a worldwide effort but the team seems to be officially based in the Netherlands. And I'm not asking my government's permission for updating either one. Trumptards and their micromanaging far-left centralized-economic-planners can go fuck themselves. Keep your damn dirty ape hands off my computers, comrade.

... a difference. What's the fear here, that they might be using your router maliciously? They might introduce some payload to attack your internal network or something similar? Aren't these already illegal, like in federal pound-me-in-the-ass illegal (well, to the extent you can prosecute some foreign state-backed actors)?

What's this going to do, the ones doing the update already have a backdoor (or a front door if you wish). This is just potentially leaving other doors open.

Also, all this small and big and feature versus bug fix ... why all the bother? Of course they can say any update is of any kind they'd like to say. I've got from much bigger vendors update after update with some nondescript (paraphrasing here) "fixing some issues" that it makes everything just for show.

I'm...curious...if Nadella's assessment of the board had to do with some deficiency in keeping minutes; or if he's just shocked into incomprehension by the idea that the board would fire you for anything aside from failing to make line go up or some really sordid sex thing that is going to reach public knowledge real soon.

For basically any employee "is lying snake who none of us can trust about anything he says" would seem like it does the job, especially with the fairly limited US requirements for firing people; so it's hard for me to see that as an obviously amateur move unless they were either chaotic in some visibly horrifying way about it; or he is just applying his own theory of what the board should and shouldn't fire you for (and to what, at least theoretically, is a nonprofit board that was supposed to be keeping the c-suite on-mission; not just appeasing the shareholders).

Arts and Humanities are fine....as pursuits of the leisure class who don't need to make living from them, or for people who work for a living to enjoy as hobbies.

Everyone is free to enjoy arts and humanities, but it's cruel to encourage expectations of gainful employment and silly to expect to
make a living from them. Confusing jobs and careers with hobbies can be financially deadly, so I didn't.

Careers fund hobbies so you can enjoy both. For example I can afford to collect and restore classic motorcycles because I did not try to make it a business. In consequence I easily afforded a well equipped personal workshop instead of starving for years to establish a financially vulnerable business. Fixing fighters paid much better.

"They appear to be pros making thousands of trades, mostly in the past year and a half, that were probably automated"
Bots are taking everyone's money? Shocking! The fact that Don Jr. is on the board means none of Trump's cronies running the bots will get banned. Heck I don't see Polymarket banning anyone as long as they're making all that money.

"In my graduation era, we were faced with the launch of the internet"
Gee lady, I'm so sorry you had to graduate when there was so much opportunity. Nobody was worried about that little screen sucking people's brains out of their eyes. In the 90's the screen had not become the plague it is now.

We can all hope that Jeff Bezos gets to go to Mars and stay there.

does anyone (govt etc) have back-door access to it?

It seems that lately governments are "insisting" on back-doors into user-encryption, going so far as to bar sales of products to their citizens that they can't just look at anytime they feel like it.

We need to read your texts to stop Terrorism! and Think of the Children!

Umm, yes fast charging and compatibility with various fast charging networks including Tesla's network is absolutely a factor in the the buying decision! Why wouldn't it?

I suspect that it depends on how strongly or weakly the 'bloat' is connected to other things; and what supporting them involves.

Something like not having TSC (which itself comes in several variants depending on whether it's from the era where you actually had 'a' CPU that just ran at a speed, or if it's one of the ones that tries to compensate for the complications of variable clocks and multiple cores) presumably comes up in a variety of nasty places related to the bad things that happen when things are not done in the expected order.

Just some random PCI device that nobody developing actually owns anymore is presumably at risk of unnoticed regressions; but (especially with the amount of PCI DNA that got carried over into PCIe or was used for the software-visible interface of some system on chip that skipped the cost of actually implementing a 32 bit parallel multidrop bus out to the PCB but either specifically sought compatibility or couldn't justify cooking up something custom when the peripherals they were integrating were all derivatives of PCI designs) it's not necessarily much maintenance overhead for it to just exist on a 'cool if it works for you' basis as a module that you probably don't need.

There's also the secondary matter of the fact that 'the kernel' has a limited number of people directly focused on its interests in the abstract; rather than some hardware vendor, distro, enthusiast, or hyperscaler's interests. If preserving hardware compatibility is directly contrary to the interests of supporting the major contemporary use case of fairly large 64 bit x86 servers and embedded ARM widgets (as 486 and pre-TSC 685-ish likely was) it's going to have relatively few friends among the people actually doing the work. If someone wants to maintain some weirdo HAM radio interface card that merely assumes the existence of PCI it's not clear anyone will go out of their way to help if they need to update something to cope with a change elsewhere; but it's not like the Ministry of Kernel is going to order them to go find bugs in the implementation of CXL memory because that's where the money is.

If these guys are actually treating a user agent string as an authentication mechanism I'm honestly surprised that being on the public internet hasn't already eaten them alive purely because of the supply of malicious opportunists; and I'll be even more surprised if it continues to work out for them now that they've drawn a fair amount of attention to it.