Isn't a bubble bursting almost certainly a correction in general? What would you have expected to see in a bubble bursting?

The 401k will just become 401.

Triggered is pretty simple. You see something and can't help but go off. This should be obvious but sometimes people are too busy being triggered to actually think

Guess what? That's how public fora work, anyone can reply, and you were talking to everyone if you didn't send some kind of private message

Edge is shit. Sometimes I have to restart it just to get it to accept clicks. And this is on a corporate machine, with no weird hacks.

It's not surprising and the roots of the problem go back to NT4. In 3.51, there were three separate memory spaces in NT: kernel, user, and GDI where graphics happened. In NT4 they merged kernel and GDI, and we began to get blue screen crashes caused by graphics drivers. These remained the primary cause of blue screens right up until the driver model changed for Vista. Browsers both came into being and got GPU acceleration in between those times, so they had the opportunity to expose bad graphics drivers.

That's not a problem for recognizing microplastics as a hazard, because we already recognize silicates as a hazard. Thanks for your support!

Compared to the rest of the costs of the systems which use it, the helium cost is not a big problem. It's less than the labor cost of keeping the machine ready for use. An MRI uses over 100 MWh a year, the machine costs millions to start with, the personnel cost is hundreds per hour... The machine uses roughly 100-200 liters of helium, which is now $30-50/liter. So $3000 to $10000 for a full fill. Boil-off rates range from 0 to 0.2%/day. A refill occurs every 6-24 months. So we're looking at a max of about $20000/year for the helium, or about 33 1/3 days of personnel costs.

(These numbers were pulled from various obviously AI-authored pieces on MRI refill costs, so they might be fairly bullshit-ish, but since multiple articles were around the same numbers I've used them here anyway.)

By the same token, management clearly either didn't understand or was unwilling to sign off on a meaningful replacement program. For that you don't just install and pray, you study what each department's users are actually doing on a daily basis and then you test the new software to determine a) whether it can actually do those things or not and b) how they are done if so. Part of that for example is to check all the templates being used to see if they will work, which they clearly didn't do here.

Office is literally designed to be hard to emulate, the so-called "standards" are bad jokes which aren't actually standards because you can't actually follow them and get an proper result. They're malicious. Not taking this into account when attempting migration is incompetent.

There is usually a difference. The headline claims executives, the summary, scientists.

Microsoft shills.

So it looks like in 3026, everyone will still be using O365, because, well - that's what they have to use.

I agree, Libre Office is a superior product. And it has gotten even better over the years. It is my daily driver, and I have O365 and Mac Numbers.

Also, if you don't run a pilot project correctly, you are going to get sketchy results. Libre world isn't all that different than O365, but yeah, you need some training. The open and save options are much greater - some might get confused. But the differences aren't even too difficult to overcome.

As I look around I see a mixture of things, some things which would be very difficult to replace, and some things which would be very easy to replace, and some things where they would still need some plastic but they could use a lot less. The rest could be made of wood or metal. Mostly I propose using aluminum because it's extremely recyclable.

Don't be obtuse, companies provide training for office applications through contracted training portals. I've "attended" video trainings on Excel and Word. If they changed to LO tomorrow I'd be fine, but I'd still have to figure out how to do those things again. And some users would not be fine.