Do the other offerings you're refering to use tailwind css?
In that case I'm also paying for continued development by the tailwind team, unlike the free offerings. I don't mind that free toolkits use tailwind, that's the beauty of the MIT license, but I do value paying something to the creators to ensure continued development. Especially if my business makes enough money from it.
I use PrimeVue, which offers it's components in Tailwind, Bootstrap, and their own CSS framework. They also offer all the components as figma files and provide actual documentation of each component unlike tailwinds 3 lines of comments for each component.
NB. I've paid for both tailwind UI and PrimeBlocks.
> Why does Tailwind not build framework agnostic UI components?
They do. As part of the original TailwindUI product you get UI component templates where you can choose between React, Vue or plain HTML (= framework agnostic!) versions of the source.
However the React version is essentially a big monolithic template, which is what they are trying to address with Catalyst, where those templates are being split up into components (+ other improvements).
Many other UI frameworks such as kendo have tried this and failed, and gone back to variants for each UI framework.
Really, if you want meaningful integration with a ui library it has to natively support that library.
I mean certainly I would be delighted if they’d figured out a way to do this, but it’s unsurprising they didn’t: it’s just a very very difficult problem to solve, and the only really decent effort at it (web components) has had extremely limited support and enthusiasm from the community, and has some reasonably unsolvable technical limitations.
Someone needs to invent a way of doing that that works before you could reasonably expect people to start building frameworks with it.
The best thing about Tailwind is everyone can use it.
Wish we could go back to the days of building for the web and not building for React.