Memorizing passwords doesn’t scale well.

You’ve likely got dozens of accounts. You’re not going to memorize a password for every account. Re-using passwords is a serious security problem though. Poorly secured sites get their password databases leaked all the time. If you use the same password on lots of sites, it’s basically a sure thing that the hashes are out there on the darkweb already along with your email, and your password is compromised.

Also, typing your email password into an unsecured library computer is a terrible idea. It is ridiculously easy for someone to install a keylogger and gather emails and passwords. In the past, your main protection was that it wasn’t worth anyone’s time to break into the computers, install keyloggers, collect lists of passwords, then figure out how to use them to get money. But with LLMs that can all be automated. It has become ridiculously cheap, and can be done by someone with a bot farm in Russia.

A password manager largely fixes the first problem, but at that point you need a device with your password manager with you to log in anyway. And the password manager doesn’t fix the second problem at all.

And… honestly, you should probably buy 3. Losing your main key only to find out that your backup key broke a month ago and you haven’t been testing it is a real risk.

They’re actually not tied to a device. They can be synced across devices.

Bitwarden, 1Password, Dashlane, Google, Apple, and Microsoft will all do passkey syncing for you.

We don’t yet have a good Linux native passkey store. I believe the credentialsd project is working on a spec for that. Once that’s up and running I would expect to see some options for syncing without relying on a third party service (though, you can self-host bitwarden right now). It’s definitely not seamless on Linux yet though.

They really aren’t a trap. They’re a well designed standard. The tooling around them isn’t quite perfect yet, but they’re a huge improvement over passwords.

People upvote because they hate change.

Yeah. Once you spend an afternoon debugging a failing cron job, the 5 minutes needed to write the boilerplate starts to feel pretty ok though.

I’ve never had to spend an afternoon debugging a failing systemd timer in the years since I made the switch.

It’s not. But the systemd timer has more robust logging and monitoring, and much more explicit and readable syntax.

Once you get used to systemd timers, it’s really hard to see why you wouldn’t use them if your system has systemd. Unless writing crontabs by hand makes you feel like a hacker I guess. I’m not even being totally sarcastic about that - there is a fun retro feel to cron.