Earlier quoted context omitted.
When using Tailwind you’re likely to use something like React components, so your actual code is more likely to look like: Dropdown button … which is even better than what Bootstrap provides since you get type safety for component props (and more opportunities for customization than what Bootstrap allows)
Type safety is good, but the class soup inside the components is just abysmal. And honestly, more often than not I see it spilling out of the components and onto the page layouts. Design tokens are the one Tailwind feature I genuinely like. Everything else – kill it with fire. Just use whatever scoped CSS your stack does ( in Svelte/Vue, Emotion in React?).
Vanilla JavaScript support for Tailwind Plus
61–70 of 202 posts
Re: Vanilla JavaScript support for Tailwind Plus
#62Re: Vanilla JavaScript support for Tailwind Plus
#63The world would be a significantly better place if someone could throw a small mountain of money at the Tailwind folks so that they can stop worrying about money and simply make the full tailwind experience freely available. There are so many lost opportunities for deep integration with other projects. Kind of like how Jeff Bezos threw a bunch of money at 37signals at some insane valuation, which helped them complete…
Re: Vanilla JavaScript support for Tailwind Plus
#64The world would be a significantly better place if someone could throw a small mountain of money at the Tailwind folks so that they can stop worrying about money and simply make the full tailwind experience freely available. There are so many lost opportunities for deep integration with other projects. Kind of like how Jeff Bezos threw a bunch of money at 37signals at some insane valuation, which helped them complete…
I think you are confused? Tailwind is already free and open source? These are just components they sale that are pre-made to save you time. It doesn’t take away much at all from the full experience?
> To pull this off, we built @tailwindplus/elements — a library we're releasing exclusively for Tailwind Plus customers.
This means if you want to use the Tailwind UI components without a Javascript framework, you have to build them all yourself, or pay.
Re: Vanilla JavaScript support for Tailwind Plus
#65Looks like it's done using standards-based web components[0]. The page says these components don't require any existing JavaScript framework; because web component support is built-in to the browser. Nice to see devs picking up web components. [0]: https://developer.mozilla.org/en-US/docs/Web/API/Web_compone...
I remember toying with Polymer circa 2014, for some reason the word "transclusion" jumps into my mind, I remember being excited about it at the time. I barely remember what it means today though.
Re: Vanilla JavaScript support for Tailwind Plus
#66Re: Vanilla JavaScript support for Tailwind Plus
#67
Lovely. Verbosity aside, now on top of knowing CSS you need to learn another hierarchical system within class names.Re: Vanilla JavaScript support for Tailwind Plus
#68Lovely. Verbosity aside, now on top of knowing CSS you need to learn another hierarchical system within class names.
Re: Vanilla JavaScript support for Tailwind Plus
#69Lovely. Verbosity aside, now on top of knowing CSS you need to learn another hierarchical system within class names.