My three Teslas were the most unreliable cars I have ever owned.

Or one could just mandate that tires contain only biodegradable ingredients. That seems an inevitable step since wheel isn't going away no matter what the level of public transportation is. Some public transit, like busses and some subways, use rubber tires today.

You could do it, but I would prefer guarantees on a per-call chain basis using a sanitizer. It should be quite easy to write.

I'm no rustc expert, but from what little I know it seems like disabling panics for a crate would be an obvious first step. You make a great point though. Turning that into a compiler assertion of "this function will never panic" would also be useful.

It’s a good first step, but half of the crates in crates.io have at least 40 transitive dependencies. Some have hundreds or thousands. A big effort.

It should be possible to write a sanitizer which verifies no panic behavior on a call graph, just as you can to verify no blocking, or no races.

None of this is newsworthy.

Due to physics, ICE vehicles are also hugely inefficient. That doesn't matter. All that matters is the cost of the fuel stock.

Engineering Explained walked through all the math: https://youtu.be/vJjKwSF9gT8?si=xZtf_ePfreOpkgr1

SF has made it work in a six month trial in 2024: https://www.power-technology.com/news/san-francisco-welcomes...

It all depends on the cost of the hydrogen, and green hydrogen costs will drop as spilled wind and solar proliferate.

due to round-trip efficiency, the running cost of green hydrogen will always be twice as expensive as just using the electricity directly for the end purpose. And where batteries are feasible, they are cheaper amortized than the equivalent hydrogen infrastructure.

Java is 3-5x slower than compiled languages, with horrible and uncontrollable tail latencies due to garbage collection. The bytecode thrashes the icache and the language is overly abstracted and too verbose. You have to install a huge runtime to use it. Many frameworks abuse the language to make things monkey patched/non-obvious. There's a reason many projects are rewritten in native languages.

Java does have a place, however, for I/O bound workloads where developer productivity matters more than performance. You can write a lot of horrible code in Java very quickly.

> Java does have a place

in fact, most projects don't have the kind of performance requirements that would make native a necessity. I say, java should be the default, and native have a place.

Confidence intervals don’t have precise timelines associated with them. Sometimes you know exactly what the problem is when you hear the symptoms.

We always balance new work versus cleanup. I always have a laundry list of beefs with my own work. You often have a sneaking suspicion that this piece of code is wrong in a manner you can’t quite put your finger on. Or you do but a new customer is trumping a hypothetical error. Or ten people are blocked waiting for you to merge some other feature. And then someone gives you a test case and you know exactly what is wrong with it. Sometimes that’s fixing a null check, an off by one error, or sorting results. And sometimes the repro case basically writes itself.

For every one of these, there are 100 which are miserable failures, where the founders would have been better off with a career at FAANG.