It is far from good enough today, no doubt. But the rate of improvement is what matters, and from personal experience I believe it is quite high. I do wish Tesla would release some better statistics.
But isn't it the case that Waymos are actually usable (for this purpose), while FSD/RoboTaxi isn't?
Geofencing sounds like a good idea to me. It's a mean to roll things out carefully, while minimizing risk of death. If actual FSD/Robotaxi is ever released, I suspect that they'll need to geofence, too, for a while.
Many of these components have been made part of the ecosystem long after they were introduced in Firefox. Also, the more platform-specific you go for each component, the more you're going to introduce subtle incompatibilities between Firefox running on different versions of Windows or in Firefox for Windows vs. macOS vs. Linux. Also, for a very, very long time, Microsoft had an extremely poor record in terms of security fixes. So what happens when you rely on a Microsoft http library and Microsoft takes a year or two to release a 0-day?
There are benefits to this approach, of course, but the costs would have been consequential.
Having done concurrency in Java and Rust, my experience is that Rust's concurrency primitives are an order of magnitude better than Java's. I haven't tested C#'s.
A long time ago, the possibility of using Java or C# in Gecko (the core of Firefox) was pondered.
Java was rejected because of the huge memory requirements and the unpredictable (and sometimes lengthy) garbage-collection pauses.
C# was rejected because (at the time) it was too tied to the Microsoft ecosystem and there was no way to get it to build on all the platforms for which Firefox is available. I don't remember garbage-collection pauses being discussed, but they would also be an issue.
reply