The problem is third party integrations, where for instance an ERP system opens integrates into Word or Office365. All those systems have to reworked by the supplier or replaces. That will be expensive - also because a lot of our IT industry is so Microsoft leaning to begin with. All our engineers are basicly tought Microsoft technologies. So getting IT people knowing Libre Office and Linux to do the integrations will be hard. Even in our pendant to high schools, most use Office365 and integrate in math and science classes with WordMat.

If it aint broke, don't fix it... Especially with safety critical stuff, upgrading is very, very hard. In general, one should do "continuous" updates, where single components are updated once in a while, but that is very expensive if the full system has to be certified again. Furthermore, old systems are often far harder to update than newer systems with better module separation.

Our wiring is based on the physical world around us, including complex social interactions. That is way more detailed and complicated than what the LLMs are trained on. Plus, we are born with a lot of pre-training or what ever evolution gave us.

Wind turbines and nuclear powerplants only take a very small area from agriculture, forests or wild nature, but solar does. And don't eat 'organic' grown food: by nor using fertiliser and pesticides, it takes a lot more area to grow the same amount of food, area which could have been forest.

But how relevant are Windows in the public/private cloud? For a lot of legacy applications of course. For CI tests if you target Windows for your product, of course. New server/cloud applications are mostly Linux. So it is getting as relevant as MacOS in the cloud over time, but time is maybe 20 years from now..

the user about a lot of crap? I just started at a job, where I got a Windoze machine. All the crap it and the IT department wants of me. Extra security restrictions even though I am admin, an outsourced IT department with full control over "my" machine. At my previous job we all used Mac and Linux, and we didn't need any IT department even though the company was 5 times larger. I understand why businesses and IT like Windoze: The feeling of control over their users/employees, and constant work for the IT department. And when something goes wrong: "You don't get fired for buying IBM ( -> MS)"

An outcome might be that no-one will bother to make new programming languages - for at least for human coders: If nobody looks at the code, assembly could be generated directly.

Well, they might be that, but sometimes people you disagree with most of the time, can also be right. I am considering myself politically to the right on many issues, but sometimes I do agree with people even on the far left.

That is the first thing they do. But they might also without admitting it, lower their prices and/or improve their services.

to add some competition to the market? The law have given the official streaming services a monopoly on popular events. I am not much interested in watching sports, so I don't care, but there is a market for very expensive services, where only the pirate services can cap the prices.

Jury trials doesn't make sense for patent trials or other complicated stuff. I kind of understand the sentiment for juries in criminal cases. If juries shall be used for patients,at least pick people working in the field as being "peers" to both sides.

Those are real OSes, you don't need to batch updates together as reboot is only required for OS updates. With Windows it makes more sense to bundle all updates as you need to reboot.

I would assume they work more hours those 9 months? Or you can claim the same of people working on offshore oil..

Most other rockets of that size succeed with minor issues in first launh. Launching the rocket shouldn't be that much different from other rockets. Re-using it is a totally other ball-game, but why not do it, how they did successfully with Falcon 9: Get it usable and then figure out re-usable. I.e. get Starship to orbit without reuse (but reuse ready), launch Starlink satellites, then reuse boosters, then start to recover and reuse the ship. Even though the development itself is iterative, it is not "agile", where you start by a minimal viable product, and then at features. This is going for all the features, before they have a product. They also seem to be caught by quality problems. And maybe they try to make it too cheap by relaxing quality too much, for instance building it outside and no clean room.

If rhe receiving company just bins the source disk, who to company? Or they loose support if they look at it?