Live data from Hacker News

Vanilla JavaScript support for Tailwind Plus

tailwindcss.com

51–60 of 202 posts

Re: Vanilla JavaScript support for Tailwind Plus

#51
Seems like this is a move to remove alpinejs from the custom block elements in tailwindcss plus? I don't see alpinejs in the code snippets anymore.

edit:

Confirmed, they removed alpine from their copy/pastable code. Now you see:

https://cdn.jsdelivr.net/npm/@tailwindplus/elements@1" type="module"> -->

This sucks because I have been using alpine and now I can't copy paste the examples ~_~

Re: Vanilla JavaScript support for Tailwind Plus

#52
post #21

Looks 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...

We use web components at the hook for my company's advertising code but I've found them pretty thoroughly disappointing, personally. They make it simple to trigger code execution but their API isn't really that good

The whole point is to make it simple to trigger code and to be interoperable. Then you write whatever code you want to implement the component.

Web components are not analogous to frameworks because frameworks tightly couple the component interface and lifecycle hooks with the component implementations. Those are properly decoupled in web components and you bring whatever rendering layer you prefer.

Re: Vanilla JavaScript support for Tailwind Plus

#53

I wouldn’t get too excited about it to be honest. At one time they were also supporting Vue but it is now basically abandoned.

This is Vue support.

With so many frameworks out there it's infeasible to build custom wrappers for them all. With web components they can build once, and work everywhere. It's only up to the frameworks to make sure they have great web components support (which just means great HTML support).

Re: Vanilla JavaScript support for Tailwind Plus

#54
post #22

The 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?

Re: Vanilla JavaScript support for Tailwind Plus

#55

I wouldn’t get too excited about it to be honest. At one time they were also supporting Vue but it is now basically abandoned.

Vue has great web component support. Even React 19 (finally!) does.

Web components are a mess but this is a great application of them: shipping reusable components that work in all frameworks. It's the one and only killer application of web components.

Frankly I'm surprised they're marketing this as "for vanilla javascript" and not as a "now supports all frameworks" type positioning.

Re: Vanilla JavaScript support for Tailwind Plus

#57

I wouldn’t get too excited about it to be honest. At one time they were also supporting Vue but it is now basically abandoned.

Vue has great web component support. Even React 19 (finally!) does. Web components are a mess but this is a great application of them: shipping reusable components that work in all frameworks. It's the one and only killer application of web components. Frankly I'm surprised they're marketing this as "for vanilla javascript" and not as a "now supports all frameworks" type positioning.

That’s not really the point. Tailwind UI depends on Headless UI. Headless UI had both Vue and React packages. The Vue package was abandoned. Many are in the process of finding workarounds for the issues or moving to another library. This new shiny thing can be used in Vue, sure. I know better now to not build anything on top of it though.

Re: Vanilla JavaScript support for Tailwind Plus

#59
post #21

Looks 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

#60
post #35
post #22

The 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…

Worried about money? They are already rich beyond their wildest dreams. They are, reasonably, excited about growing and expanding and building a company that does much more, but that is not driven by a need for money, it is driven by their ambition. edit: I can’t speak for Adam etc., this is just my impression. My impression is that they want to build a business of which tailwind (the open source project) is one part…

interesting, i had just watched Primeagens Standup with Adam and got the impression they don't do well for money, but a quick google came up with a bunch of posts from Adam himself disclosing some fairly impressive numbers.

No idea if he still does ok from it, but he certainly did at one stage.

Post reply on HN