It's a little scary how widely used Radix still is (and by extension shadcn/ui) even though WorkOS has essentially left it to rot. @vercel.com needs to acquire and/or fund it at the very least.

Recently published my first Rust library for managing custom Windows context menu entries -- something I do often manually, so I wanted to build something to make it easier.

Rust is an incredible language. As someone who started with JS, getting into low-level languages was difficult, but Rust makes things just easy enough.

I've been doing web development for well over a decade and I just now found out about array URL search parameters ("param[]=foo&param[]=bar"). Either I'm living under a rock or this really isn't common at all. I've used plenty of APIs that take arrays as a string of comma-separated values.

Impostor syndrome seems like it’s at an all-time high in software dev. Been hearing so many stories about it lately. Horrible feeling.

It seems the biggest argument against Tailwind at this point is still class pollution, but as long as you structure your components correctly by abstracting any repetitive tags, it's entirely a non-issue. In any case, separate CSS styles are objectively bad.

CSS has so many incredible new features (not fully supported yet) that will make front end dev much easier.

- “calc-size()” for transitioning to intrinsic values like “auto”.
- “@starting-style” for defining the initial style of a newly displayed element.
- “@scope” for faux selector specificity.

I’ve always been a huge proponent of JavaScript as a first language.

Entirely usable within any web browser and loosely typed.

I hear a lot of arguments for Python, but really anything that requires an environment to be set up (compiler paths, IDEs, etc.) is already too complicated.

Learning how to properly use React Query with Next.js SSR is like running a marathon. Even as a long-time React dev, some of the paradigms are challenging to fully grasp.