1) It can't be that replacing 20 C/C++ shared objects with 20 Rust shared objects results in 20 copies of the Rust standard library and other dependencies that those Rust libraries pull in. But, today, that is what happens. For some situations, this is too much of a memory usage regression to be tolerable.
2) If you really have 20 libraries calling into one another using C ABI, then you end up with manual memory management and manual buffer offset management everywhere even if you rewrite the innards in Rust. So long as Rust doesn't have a safe ABI, the upside of a Rust rewrite might be too low in terms of safety/security gained to be worth doing
Many Rust core/standard library functions are trivial and inlining them is not really a concern. For those that do involve significant amount of code, C ABI-compatible code could be exported from some .so dynamic object, with only a small safe wrapper being statically linked.
Meanwhile, in real life San Francisco, I much prefer being around Waymos as a pedestrian and cyclist than human drivers. While most human drivers are competent and considerate, a small percentage are not -- and given the number of encounters in a single trip, I have these dangerous interactions weekly.
Despite being a noticeable presence on the roads, Waymos have not contributed to congestion at all as far as I can tell.
He's really excellent at faking it until he makes it. That, and sucking down government funds. SpaceX, Tesla, NeuraLink, and Boring Company all relied or rely on subsidies or government contracts.
An actual car company would not have the market cap of Tesla. It's all hopes and dreams, of which Elon apparently is an excellent purveyor.
This administration, to put it mildly, does not have the trust of most Americans when it comes to fair enforcement of the law. That's the consequence of their own behavior.
Though let's be realistic, here: $600 is much more than the typical school-assigned Chromebook.
reply