To me it seems there's more to this story. The crash happened at 1:10 am on a highway in Utah. I imagine there was no traffic at that time. Most likely there were only this motorcycle and the Tesla, and at most a few other cars over a good stretch of highway. When there's no traffic, motorcycles tend to go faster than cars. A Tesla on autopilot either respects the speed limit (factory setting), or it can be programmed by the owner to allow a bit above, just like the regular traffic flow. Let's say 10 mph above speed limit. It seems quite unlikely the motorcycle was doing less than that speed, so how exactly did the Tesla rear-end the motorcycle? Also, how did the driver of the Tesla "not see" the motorcycle? You drive on a highway with the headlights on, there's a motorcycle in front of you with taillight on, how can you not see it?

I can see some possibilities: - reduced visibility because of fog, or some other reasons - the motorcycle rider was driving under the influence, and made some sudden move that the Tesla autopilot was not trained to predict (e.g. aggressive cutting in front of the vehicle) - somewhat similar: the motorcycle rider lost control of his own vehicle for whatever reasons, and the Tesla rear-ended them while they were skidding on the pavement - the Tesla owner had overridden the autopilot speed limit factory setting by 20 mph more - Tesla was not on autopilot at all, and the owner is simply lying; maybe the owner was DUI - a case of road rage: the biker did something, the Tesla guy honked, the thing escalated, maybe both were a bit inebriated, and the Tesla guy rear-ends the biker not with the intention to kill, but just to "teach the guy a lesson"

I'm not trying to say Tesla is not at fault. In the first 4 cases I listed, Tesla is clearly culpable.

I just simply doubt the story is "biker riding normally, and suddenly a speeding Tesla rear-ends and kills him out of the blue". At 1:10 am on a nearly empty highway.

I would worry if people started moving away from Emacs as text-centric. My biggest complaint with VSCode (which I do fully expect to take over and to which I will one day presumably have to migrate) is that there's so much damn UI for things. The terminal window isn't just a buffer of text like everything else, it's its own ungodly window that pops up differently. Most extensions are primarily UI instead of keyboard and text driven. There's a nice Magit clone which does things properly, and I'd love to see more effort on things like that. But fundamentally VSCode doesn't seem to have the right level of abstraction to allow all this.

Has the problem of having to recharge rapidly been solved?

What if I need to drive somewhere in a hurry but my car isn't charged?

What if there's a power outage or I forget to plug in my car overnight?

I'm not saying these are blockers, but they're not convenient.

As I read this, I can't help but think of how much easier it would be to get a "regular" Linux distribution running on most of the MikroTik routers if they would upstream -- or release or even publish -- their changes, kernel configurations, and such.

Instead, they're basically selling devices running a "proprietary" Linux and, IMO, leeching off of the kernel development community and others.

Fortunately, the OpenWRT community has, over the years, managed to get OpenWRT running on many of the MikroTik devices. (Occasionally, depending on the particular device, there's a "performance hit" due to hardware acceleration that doesn't work without binary blobs from the vendor, for example, but they've certainly managed to make these devices for those of us who would prefer to not touch RouterOS!)