francislavoie

Sure, but projects need to start somewhere. You can't go from one user to hundreds+ without first having two users. This is how they're deciding to share it the first time, and that's fine. Use it if you like, don't if you don't. Simple. If they stop maintaining it, then since it's open source and MIT license, you can do what you want with it to fix the issues you have.

I don't see it the same way. People are building these things for themselves because it solves a specific problem they have, and that means it's crafted just to their liking. And it will only become easier to maintain these because of LLMs constantly advancing (for now). So if this is also a match for what you want out of a tool, then you can easily adopt it, or even fork it to your own liking. If it's not a fit for you, that's fine, there are plenty other options that may be.

A new one but they're merging it with Theo's.

I've been doing this with bun lately, single file app with built in SQLite. JS runtime which serves the app with SSR, websockets, and all that good stuff. The binary size is not that small, but that's usually worth the convenience.

Worth noting, Tailwind was canadian, and Shopify is also canadian. I like that this was the outcome. The labs business was obviously no longer needed in this era of AI, and I'm glad Tailwind will continue to get proper backing from Shopify to evolve further.

Language Server Protocol, it's what your IDE (like VSCode or other) uses to do linting, syntax checking, and "go to reference" stuff.

Can be a TUI, can be a GUI.

A "harness" is basically what you call Claude Code and such, i.e. a TUI to run the agent.

The component itself is the semantics, adding naming over CSS classes adds no value whatsoever, only adds cognitive load and requirement of context switching to understand "what does this named class actually do?"

I disagree. I don't want to jump between two files constantly. With Tailwind I can stick to one file and never need to think about naming things.

Your complaint is about bad developers, not about Tailwind. Using Tailwind correctly means making heavy use of components to avoid duplication. Using Tailwind also removes the burden of having to do one of the hardest things in software: naming things, which is what semantic classes requires you to do.

I would reach for class-variance-authority (aka cva) instead for stuff like a size prop, it declaratively solves that.

Absolutely not. Semantic classes are the wrong way to go. Your components (and their props API) are what encode the semantics. With Tailwind you never need to try to come up with a name for anything relating to style, you just use utility classes. It reduces cognitive load significantly.