chrchr

I'm not an expert, but it's frustrating to read these threads about passkeys. The common objection I see here is "But if I lose my device I'm locked out!"

A lost passkey should be treated the same as a lost password.

Sites that implement passkeys need to have an account recovery mechanism. Granted, not every site does this correctly. Don't use passkeys on sites that don't have a recovery mechanism!

Secondly, the site you're authenticating to must allow you to have multiple passkeys. You either have a cloud-synced password manager so that all of your devices get the same passkey, or you have a passkey per device that you use to access the site. Again, not every site allows multiple passkeys. Don't use passkeys on sites that don't allow you to have multiple passkeys.

For a site implements both of these properties correctly, if you lose your device, you just connect to the site with your new device, perform whatever account recovery procedure (TOTP, email verification, phone verification, ...), create a new passkey, and, ideally, disable the passkey from your lost device.

Test driven developmet practitioners in Smalltalk used to (still do?) write the test before writing the implementation, run the test, and, when the "method not implemented" error shows up in the debugger, type the implementation and continue the execution. Common Lisp can do that too.

So, in practice, it might look like you hit any kind of runtime failure, and then the LLM writes some code to fix it, and the user's request completes successfully with no errors.

This is Noctalia 5. It's a complete, standalone shell with no Quickshell dependency.

I don't think people even read the blog post, because the blog post pretty clearly explains that Laya isn't really comparable to Jev.

I vividly remember the months after AMD64 came out when tech companies were dumping their specialty RISC server hardware (mostly Sun, but some other stuff too) and replacing them with commodity AMD boxes. It was felt like a monumental shift.

Interestingly, this device uses a totally different mechanism than classic trackpoints. Where true trackpoints use a network of strain gauges on the PCB, this is a 3D hall effect sensor and a spring. A trackpoint has only an imperceptible amount of travel, and this is designed to physically move. I really wonder how it feels in practice. It might feel more like a thumb stick from a game controller than a trackpoint.

It's funny that they call it "reverse game theory", like it's a new thing, when it's actually just regular game theory.

Amazon developers use similar devboxes. I think it is mostly so that developers can use a production-like Linux environment with integrated Amazon dev tooling. You're not required to use a devbox, but it can be easier and more convenient than running stuff on your laptop.

"Everybody on earth knowing that beauty is beautiful makes ugliness."

That resonates with so much of the discussion on this site. We're all trying to make good technology that helps people! Why does it so often fall short?

But your friend is wrong. She does know at least one person who comments on online forums. I bet she knows more too.