You need to be comfortable with Rust and with ECS.

If you’re coming from a GC language and `Player extends Entity` mutable OOP approach, you will have to completely re-learn how you architect games.

The upside is that Rust is pretty fast, and Bevy takes advantage of Rust’s relatively easy multi-threading.

I think another solution could be to use an arena/memory pool to replace indices with references.

But indices are still safer than raw pointers - vec access does bounds checks. You can make indices typed if you’re worried about mixing them up.

I mentioned slab/bump allocators in the README. But whether it works with the Ptrlist type punning is unclear to me.

Historically, there has been a bigger trade-off between safety and performance, and performance has been much more important.

Besides, there are many many factors determining successes of OSes, often far removed from quality of the software itself (1986 AmigaOS had GUI and multitasking, and still lost to MS-DOS and Windows 3.1).

All mistakes is such an unachievable high bar, it’s almost a strawman argument. You can always imagine a programmer terrible enough that they will find every possible failure case.

However, Rust can prevent quite a lot of common mistakes. Getting rid of UAF, data races, and having deterministic destruction that unlocks locks is already a major quality improvement.

Rust can’t prevent deadlocks caused by wrong architecture, but of all concurrency issues deadlocks are the easiest to diagnose.

> You can always imagine a programmer terrible enough that they will find every possible failure case.

Uhh, no. That is an amazing programmer! Why? Because truly terrible programmers imagine a subset of every possible failure case and simply refuse to acknowledge other failure cases, especially the ones that are particularly common with particularly severe consequences.

I wonder what’s the API/ABI of that OS. This is where the language does make a difference.

On most systems the C ABI has been the only ABI for so long that people have forgotten system ABIs are language-specific.

IIRC there is supposed to be a failover to AMS.

Just build more off-shore wind, and grid interconnect.

I want the full Thunderbolt and macOS on my phone.

The common sentiment here is that all electronics should be ripped out of the cars, but I think the solution should be for car manufacturers to recognize that UX and software quality matters.

All legacy manufacturers seem to treat software with contempt, as some sort of unimportant annoyance that only needs to be implemented to minimum spec, and has no purpose other than getting regulators off their back, plus maybe looking pretty in the showroom.

Someone has probably written a checklist with "the car must beep whenever the seatbelt is not fastened", sent it to developers in the lowest basement level, they've checked it off checklist, and nobody has given a second thought about how dumb that is when taken literally.

Auto manufacturers don't have the skills to design or implement good UX, and they don't have the leadership with the skills required to hire the people with the right skills.

or rather: their customers don't care and keep buying what they churn out anyway, so they have no incentive to change

I feel like the pretty massive consumer support of Apple CarPlay/Android Auto, to the point where supporting it is sometimes used as an explicit marketing element, is a sign to the contrary.

When they're all enshittified like this, what are you going to do? Be the one person without a car? That'll show 'em!

We'll find out soon enough, won't we. Or at least GM will.

"Backlash" is a weird way of phrasing it. They're slashing net metering, and only for new instillations.

That seems entirely reasonable to me. It doesn't hurt people who've already installed panels with net metering priced in their ROI. And not paying for electricity when there's already a surplus seems economically sensible. Subsidies for panel installations could be more direct, and/or could encourage solar+battery installations to give power to the grid when it's actually needed.