samus

The really valuable CRUD monkeys are already domain experts as well. The threatened ones are junior developers whose output is barely better than AI slop.

Steam and most other nontrivial applications use other open source components internally. Those need funding as well.

It's an unfair fear since architecturally Wine sits at the same position as the Win32 API on Windows, which also in the end merely uses the underlying native system calls. The only difference is that Linux aims to keep its system call interface stable.

Any appliance with strong motors should be more efficient with AC supply. But almost anything else can be regarded as a heater that doesn't care much as long as it is fed with the correct voltage. Which is actually the core issue.

A DC household would have to choose a trade-off between multiple lines with different voltages or fewer voltages that need to be adapted to the appliances. And we're right back at the AC situation, but worse since DC voltages are more difficult to change.

But consumers like datacenters can very well plan ahead and standardize on a single DC voltage. They already need beefy equipment to deal with interruptions, power sourges, non-sinus components, and brownouts, which already involves transformers, condensators, and DC conversion for battery storage. Therefore almost no additional equipment is required.

The typical IoT company not surviving the typical lifecycle of their products shows that IoT is a seriously dorked up idea. Anybody deploying them who values security should choose products that can be updated even after the vendor is gone.

> How are you going to use a warranty from a company that no longer exists to get a security update for a product a million consumers still have?

I was not talking about using warranty for this.

> And "require longer support" doesn't fix it because many of the vendors will go out of business.

Which is not a real issue in practice. It's like arguing that warranty doesn't matter because the vendor might go out of business.

> in favour of less fossil fuel production elsewhere?

Another slight tangent: the street of Hormuz being closed has them covered nicely there currently.

There are undecidable situations in Minesweeper.

Last time I checked, only the US and Israel. Europeans don't want anything to do with this war, and the USA's East Asian allies also like it not even a little bit.

> Declare victory, say the straight is open, just like the Red Sea is open. If anything moves at shipping, destroy its source.

Do you understand the concept of asymmetrical warfare? Hiding hundreds of launchers, firing them, and losing them is already accounted for by Iran, while a decent chance of losing any asset going through is prohibitively expensive. The strait is closed.

The risk of being targeted by missiles or drones works just as well. There is a reason NATO has to patrol the Red Sea with warships.

They don't really care what happens afterwards. They openly admitted that a Libya-like situation would be preferable compared to leaving the current regime in power. Whether that's actually a strategically valid assessment is a completely different question.

East Asian economies are severely affected by high fuel prices. People need it to fuel their boats, to get to work, and to heat their homes. And it's the input to many critical industries, most importantly to make fertilizer. Not all countries's stockpiles are large enough to sit this out.

Right until the end I thought the guy was doing a social engineering penetration test, checking whether he could brow beat the server admins into bending over backwards to reveal this information.

Quite the contrary: an empty countryside would make invasions harder because there would be no infrastructure: no roads, no bridges, no tunnels, no electricity, no water supply, no opportunities for shelter. Everything would have to be shipped from outside or built by combat engineers, putting an immense strain on logistics and slowing operations to a crawl.

Small town are usually quite affordable because they offer fewer high-paying jobs. Remote work is by far not yet common enough.

> We subsidize food production. Electricity and water distribution is subsidized by urban customers.

These things usually happen far outside of the cities. Without infrastructure for the countryside these things would not happen.

Once introduced, keywords and Java syntax is nearly impossible to change or to remove. If it's possible to get the job done using a class, perhaps with some JVM magic, it's not wise to whip out new syntax.

There might also be many optimization opportunities that still have to be seized.

The same technology can also be used to force people to live with bodies engineered to make their existence a living hell. Similar things can be done with brain uploads.

I fully understand why the courts are slow, and they should indeed not rush decisions (especially since they have a huge weight in common law law systems), but because of this they are not able to restrain another powerful institution that has no problem with moving fast and breaking things.

That's true in theory, but really missing the point. In practice these checks come far too late. The court system is notoriously overworked and slow. In this case, most of these tariffs will not be returned because the government will make it an administrative nightmare to claim it back. In other matters the damage is even harder to roll back.

It really depends on what you're doing with your hardware. Overclocking, overheating, unstable power supply, and things like that increase the likelihood of memory bitflips.

It makes economic sense to keep selling non-ECC hardware to maintain market segmentation.

Maybe a partial solution would be to duplicate pointer data, compare pointers at every deference and panics if it doesn't match up. In essence a poor man's version of ECC. It's a considerable runtime overhead, but it might be possible to hide it behind a flag, only to be turned on to reproduce bugs. Also, anti-cheat measures already do something similar.

Certain data is more sensitive as well and requires extra protection. Pointers and indexes obviously, which might send the whole application on a wild goose chase around memory. But also machine code, especially JIT-generated traces, is worth to be checksummed and verified before executing it.

They probably should have been. But the presidential system putting de-facto unchecked power into the president is just asking for such abuses to happen. Almost by design one might think.

You might anyway have to check them out so you can review them in depth. PR can give you an overview of what changed, but only very limited insight into the context of the change, and no oversight at all into whether something is missing.

If your code is modularized then you have at least protection from modules polluting each other's packages.

I rather hope it doesn't. It's not so much about action; it's subtle worldbuilding and a certain vibe that is easily distorted on screen. Also, it would destroy everybody's personal vision of the Shrike...

I find it awesome that the true nature and mission of the Shrike remains a secret.