Also, anything sounds big when you put it in gallons. Doesn't sound so big when you mention that's 92 acre feet, the amount used by less than 20 acres / 8 hectares of alfalfa per year. Or when you mention that a typical *closed loop* 1GW nuclear reactor uses 6-20 billion gallons of cooling water per year (once-through uses 200-500 billion gallons, though most of that is returned, whereas closed loop evaporates it)

I don't think it has anything to do with that. As soon as I saw the headline, my mind went "cohort study". And sure enough, yeah, it's a cohort study. Remember that big thing about how wine improves your health, and then it turned out to just be that people who drink wine tend to be wealthier and thus have better health outcomes? And also, the "sick quitter" effect, where people who are in worse health would tend to stop drinking, so you ended up with extra sick people in the non-wine group? Same sort of thing. This study says they're controlling for a wide range of factors, but I'd put money on it just being the same sort of spurious correlations.

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).

I don't need 1000 miles. 600 (unencumbered) is definitely sufficient, and 500 might be okay. The thing is that I'll lose half to 2/3 of that range when towing my camp trailer, and that's not even considering that I'm typically towing it up into the mountains, gaining ~5000 vertical feet. I also need minimum 12k pounds of towing capacity and I'd like a little headroom, so call it 16k, and the bed payload has to be able to take at least 2000 pounds, because that's how much the trailer puts on the fifth-wheel hitch.

I'm anxiously awaiting an EV pickup that can do this. I'd love to have essentially unllimited electricity to buffer cloudy days (I have 1 kW of solar panels on the trailer and on sunny days they generate way more than enough, but consecutive cloudy days can leave be difficult).

3/4 ton and 1-ton gas and diesel pickups typically have oversized fuel tanks that provide about 600 miles of range, because that's what you actually need when you start hauling or towing significant loads. I don't think an EV pickup needs to have more range, but it needs to be comparable, and to be able to tow and haul comparable loads.

I'm not anti-EV by any means. I bought my first EV in 2011, and have had electric cars ever since. Trucks are a different sort of problem, though.

That's getting there, though I'd like to see some driving tests with a good-sized fifth wheel at highway speeds. The towing capacity is probably okay, though it provides very little headroom for when I'm towing both my camp trailer (~8k) and my boat (~3.5k), which I actually do several times each summer. But I think the payload capacity is too small to tow the trailer, which puts about 2000 points on the truck.

When CUDA started taking off we had ATI hardware, to support their open source pledge, and looked into ROCm.

Just getting the drivers to build on EL-anything was an extreme effort, and it wasn't my first rodeo.

Without betraying confidences, I was told second-hand that there were only ten people on the GPU driver team across all platforms and that they were doing their best and not sleeping enough as it was, with Compute way behind gaming bugs on the priority list.

I couldn't independently verify of course but the theory fit the data.

I immediately empathized with the suffering of the devs and went out and bought nVidia cards, annoying binary drivers and all.

Since then I've felt like that some bean counter at AMD wrote nVidia a trillion dollar check.

If you're not a tiny company *overstaff* your engineering departments so you don't miss new opportunities as they arise. The opportunity costs exceed the opex costs.

Same here but this lack of support will matter much less than dropping i486.

There are still embedded systems sold today that only meet i486 specs. I don't use them but some industries do.

Sure a $12 ESP32 can handle those tasks but it's a revalidation thing.

Not that anybody from those vendors stepped forward to maintain a tree.

OTR might be small enough.

The Axolotl Ratchet is much better but perhaps too big for SMS.

TextSecure probably would have offered it were that feasible.

Of course if you can arrange one-time pads you're 1:1 at 140 characters.

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.

Agreed. My sedan has been electric for nearly a decade now, but I'm still driving a diesel pickup (1-ton, though a 3/4 ton would be sufficient) because EV pickup range is inadequate -- and I think it may be inadequate for a while. I need 250 miles of range when towing a trailer, which means I need ~500 -- maybe 600 -- miles of range without.

I'm not generally a fan of hybrids, but I think plug-in hybrids with large-ish batteries may be the sweet spot for a while with pickups. The Dodge Ramcharger is looking really good to me, though I'd like to see them make a 2500.

"I just put my models on a usb drive then plug said drive into the printer."

You must have a lot of spare time on your hands.

"It works great locally" - Um, no it doesn't?

They've made a nice easy-to-use ecosystem. For $400 you can get a P1S that supports adding an AMS, auto bed leveling, enclosed-chamber printing, high precision, high print speeds, and 300/100C nozzle/plate temps, and has an easy cloud print service and a robust ecosystem of models you can just download and print with no extra config straight from the app.

But yeah, their behavior is increasingly entering bad-actor territory. I wonder how long it'll be before they lock entry-level printers into their branded filament?

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.

Really this is far more probable than a dozen people went crazy in the same way at the same time which seems to be a plurality of comments.

If there's an American great ape they live in Washington state, not Ohio, based on report frequency.

Star Wars nerds? Yes, so many in Ohio.