Right. And to be clear, I'm not saying that's a bad thing. Maybe those scientists should have been punished for their part in the atrocities, but making something actually useful from those weapons was a good thing.

They wear out and need to be replaced. Demand was low, AI increased demand, but the manufacturers see it as a bubble and aren't going to massively ramp out output to meet it.

This reminds me of when Germany built new coal plants and there was much hand wringing. In fact they closed more than they opened, and the new ones were designed to fit better into a heavily renewable grid.

Another good reason to invest in solar. The more energy you generate yourself, the less you are beholden to whatever they want to charge you for it.

It's just how they organize it. You wouldn't say NASA is a military organization because its funding is authorized by congress that also authorizes military spending, or because the president is also the Commander in Chief.

Some countries maintain the fig leaf of separate military and civilian space programmes, but that's all it is. For example the Space Shuttle was designed around military payload needs, and regularly used to deploy military satellites.

For decades all the US astronauts were ex military test pilots too, and of course a lot of military rockets/missiles were used in the early days. Most of the rocket tech was derived from Nazi weapons.

They have been letting women fly from the get-go too.

I'm glad Oracle is keeping the async pollution out of Java. Java is more of a business or admin domain language, and less for systems software. You don't really need that for biz/admin coding, and there are ways to still implement for the rare cases.

I guess I'm not working on "typical CRUD apps" then?

Based on your description, no, you are not, other than maybe "data stores". Sounds like systems programming. And it's rare to need such for app-level database access (unless you did something wrong or bad).

other than async and await keywords here and there.

It tends to force the need to parts that have nothing to do with asynchronous programming other than being referenced by parts that do. It pollutes and spreads like prions in a brain.

... which, to be clear, is a good thing. Working around the compiler is dangerous and a code smell, so it shouldn't be something that is easy to do. It usually indicates that either the compiler's capabilities aren't sufficient to meet your needs (in which case, a better solution would be either a better compiler, or to re-evaluate the wisdom of your approach), or that you are doing something the wrong way and should find a way to do it that works with the compiler, rather than around it, so that you get the benefits of the compiler's co-operation.

Elon likes his rocket toys, and thus needs money.

Apple. Going out of business since 1977......

Doesn't Elon's pay depend on Tesla revenue? If for example BYD kicks Tesla's ass, Elon gets lackluster pay.

Java's Mono library is a poor substitute for C#'s async/await keywords

The Async/await stuff is just syntactical bloat for most typical CRUD apps. I suspect it's there to help MS save on cloud costs, rarely helps devs.

I was surprised to see Delphi on the list, let alone ahead of SQL.

I can't read your post because the ad covers half of it up.

We got it.

Then played some more (;