Very cool, I like the idea, reminds me of css modules in react, but easier. Or svelte/vue css. Its weird to compare this to tailwind and say it’s a simpler abs

Very cool, I like the idea, reminds me of css modules in react, but easier. Or svelte/vue css. Its weird to compare this to tailwind and say it’s a simpler abstraction though. This requires JS on the client, whereas tailwind does not. This modifies the css styles you write at runtime, tailwind does not. > Tailwind verbosity goes up with more child elements True, but in component-driven design this does not happen in source code at least. The tailwind classes are only defined in each component, not the usages. > No chance of deprecations. 16 lines is infinitely maintainable. Ridiculous claim, sorry. Those 16 lines aren’t trivial, aren’t tested, aren’t formatted (would be more like 30-40 lines I would think) Anyway, I’m impressed with the idea and concept behind it. Good work on implementing it!