I'm not a fan of Tailwind's approach if I'm being honest, and while at first glance they look similar, from a practical standpoint Turbo is something I can actually see myself using to create landing pages and design systems without having to conform to Tailwind's insane naming scheme. The conditional styling also looks very intuitive.
To that end I appreciate the Turbo vs Tailwind page, and I'll definitely take this for a spin at some point (not having to explicitly exclude Sass or remove unused styles seems like a refreshing way to handle performance).
The in-browser compiler is also something I've never seen before, and from what I'm understanding that makes it extremely portable; no package manager necessary.
Great stuff. I liked it much better than Tailwind after a quick try. Too bad can't use it because part of my project is a "visual editor".
> You are not allowed to use the Software in creating a website builder, website editor, visual editor or visual development environment, except on the Boomla Platform.
I - honest to God - think that this isn't a good idea: it makes the HTML basically unreadable, plus if you end mixing up Turbo and plain CSS sheets it's gonna be a manteinability mess since you have to costantly look on (at least!) two different places.
Interesting, that's exactly the opposite of my experience. First off I'm not writing plain CSS any more, at all. It's just so much more cumbersome. Maintenance is 100x easier as I don't make unintended side-effects. Btw, did you notice you can also build your own higher level classes like buttons with it? That helps with keeping your design system coherent.
I'm not a fan of Tailwind's approach if I'm being honest, and while at first glance they look similar, from a practical standpoint Turbo is something I can actually see myself using to create landing pages and design systems without having to conform to Tailwind's insane naming scheme. The conditional styling also looks very intuitive.
To that end I appreciate the Turbo vs Tailwind page, and I'll definitely take this for a spin at some point (not having to explicitly exclude Sass or remove unused styles seems like a refreshing way to handle performance).
The in-browser compiler is also something I've never seen before, and from what I'm understanding that makes it extremely portable; no package manager necessary.