@armandososa.bsky.social

The entire basic API of Keyboardist: import { createListener } from "keyboardist" const listener = createListener() const sub = listener.subscribe("Slash", focusSearch) sub.unsubscribe() Zero deps, ~3 kB, npm install keyboardist. keyboardist.io

Bild

unpopular opinion: I know NextJS is all the rage. But I think laravel/inertia is a better stack, specially for side projects. No surprise bills. No "use server' incantations. LLMs can build backends with zero drama.

Shadcn ui is great. Problem is that it's so good that it hides bad ux design. Just because it's pretty, balanced, and readable doesn't mean that the design underneath is good.

I think basecamp 1.0 was the perfect app for simple project management. Everything else is just to justify the existence of the parent company.

I've been trying the vertical "tabs" in Chrome and I don't quite like it. I don't know if it's only because I've been using horizontal tabs form 20+ years and this is resistance to change

I’m not a fan of most React localization libraries. For my day-job, I developed my own system, but for personal endeavors, I’ve been using react-intl, and I feel a bit resentful towards it. I’m considering creating an open-source version of my approach for our app.

I've been experimenting with turning my browser game into a PWA and I'm not convinced that it's worth the effort. I asked Claude iits opinion and while I wasn't surprised by the answer (no, I shouldn't do it), I was surprised by the comedic timing of the ellipsis at the end of its response.

The only scenario where I'd reconsider is if you had a strong reason to support offline play on the web specifically — but even then, for a game, I'd question whether offline web is really a user need worth that cost.
You'd essentially be adding a third surface to maintain for a marginal UX gain over just… opening a browser tab.