I'm more concerned about the failure mode than the failure rates. Mechanical and hydraulic brakes can experience gradual failure, giving the driver a chance to pull over get the car repaired.

EVs usually have a single motor and a single inverter , both of which can fail suddenly. Electronics usually work perfectly fine until they suddenly don't work at all (blown fuse, bad connection, blown capacitor etc)

How are they gonna build redundancy so that no single component failure means youre freewheeling downhill on the highway

Well that sounds terrifying. There's a reason why the brake hydraulicsystem is actually two separate hydraulic systems, for diagonally opposite wheels. The only single-point-of-failure is the brake pedal.

Their leaving out the critical details on how this will electric system will be fail safe, or even legal.

The announcement was light on details about both the system itself and how its fail-safes are implemented.

Maybe they'll return to spring actuated mechanical brakes that are released when everything is working. (More common in heavy industry, and I believe also truck brakes)

A key for each service for each device is too impractical in real life.

Getting a new device would mean logging in to hundreds of services to link up the new device. Or somehow keep track of which services have keys with which devices. And signing up to a new service would mean having to remember to generate keys for a a handfull of devices, some of which might not be available at the time (like a desktop computer at home when you are out). Or you risk getting logged out if you loose the one device that had a key for that particular service.

I agree passkeys can make sense with something like BitWarden or KeyPassX. Something that is FOSS, and is OS and device agnostic, and let's you sync keys across devices. And should have independent backups too. Sync is not backup.

I use BitWarden too. OS , device and browser agnostic is a win

But I imagine the vast amount of people will use whatever their platform is pushing, so Apple Google or Microsoft. And in 5 years time "3rd party passkeys" are not "secure enough" and blocked by the OS. (Ok that's a bit tinfoil hat, but Google's recent Android app developer verification scheme is fresh in mind)

The biggest disadvantage:

Disadvantages of Passkeys

Ecosystem Lock-In – Passkey pairs are synced through each vendor’s respective clouds via end-to-end encryption to facilitate seamless access multiple devices.

More eggs in the American megacorp basket for more people, yay

Space Engineers have a guide for that:

Tech dirt's stepping up and arguing for actual journalism:

Let’s be clear: uncritically reporting the White House’s “nothing to see here” stance isn’t journalism — it’s stenography.

The media’s job isn’t to parrot White House talking points — it’s to uncover the truth.

How come?

From the article:

In a statement, the police in Finland said the authorities had boarded the Eagle S tanker in Finnish waters.

So no international waters in this case. In fact there are no international waters in the Baltic Sea ( https://en.m.wikipedia.org/wiki/International_waters )

It's hard to write and hard to read. The forced joining of every single letter in a word quicky makes it unintelligible unless your handwriting is perfect or you write very slowly

Flashback to ~2008-2009 when all laptops went from 16:10 to 16:9 and we couldn't understand why. 16:9 was for TVs and watching movies. 16:10 was for computers to do work.

While it's true finding 16:9 desktop backgrounds is easier, and watching movies and TVs without black bars is nice, 16:10 is much nice when actually using a computer to do work. Taskbars, toolbars, tabbars, headersbars etc take up a lot of precious vertical space, leaving less space for application content.

Simply put, X11 is the bottom of the graphics stack, i.e. everything that makes Linux have more than just a command line has historically been built on top of X11

X11 is OLD. Like really old. And has a bunch of problem because of it (no variable refresh rate, no good multi monitor support, no proper fractional scaling , tearing, no security etc) It's also very mature. Somehow developers have managed to build a decent user experience out of the old X11

The Wayland protocol was designed to overcome the shortcomings of X11 and replace it. Wayland is now at the cusp of being a fully functional complete replacement for X11. It already is for many (most?) use cases.

Many Applications that are not made for Wayland will still run in Wayland, but they run in a fake X11 server inside called Xwayland. But native Wayland is better (performance, security, features)

Wayland very good on AMD and Intel these days. Nvidia was unsupported, but last year nVidia made a business decision to support EGL(?) so with fresh drives work has begun in Gnome and KDE to support Nvidia in Wayland. I'm not sure how mature Nvidia on Wayland is yet