Tailwind is fine, but I do find it humorous that they discourage wrapping up tw classes into a component class ala Bootstrap, but they wrap html up like this: Options ... Bootstrap: Dropdown button ... (I realize you have full control over looks with TW, but Bootstrap and others have utility classes too for the common stuff.)
Vanilla JavaScript support for Tailwind Plus
31–40 of 202 posts
Re: Vanilla JavaScript support for Tailwind Plus
#32Would love to know how they went about implementing these. I always find custom elements interesting. I know the guys over at data-star.dev used one to implement their inspector element, but unfortunately that is also behind pro. I know Lit is used a lot but I’m always looking for new approaches.
It's explained in the post.
That has implications for event handling and style encapsulation.
Re: Vanilla JavaScript support for Tailwind Plus
#33But I understand that funding open source is never easy & I still appreciate tailwind from the bottom of my heart simply because some might hate it for what it is, but I appreciate that I have options to being with (daisy,tailwind etc.)
If anyone who has ever contributed to open source is reading this. Thanks. I am a real frugal person but one day, I want to earn enough money that I can donate to you guys without hesitation and be an open source contributor too.
Re: Vanilla JavaScript support for Tailwind Plus
#34Earlier quoted context omitted.
It's explained in the post.
They don’t mention whether the custom elements are using shadow root and whether it’s open or closed mode. That has implications for event handling and style encapsulation.
Re: Vanilla JavaScript support for Tailwind Plus
#35The 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…
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. I think that regardless of money in the bank they would want to have revenue generating projects. Laravel is a good comparable.
Re: Vanilla JavaScript support for Tailwind Plus
#36The 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…
The “full Tailwind experience” is already freely available. What “lost opportunities for deep integration” is a frontend CSS framework missing? Tailwind Plus (the commercial product) is like buying an off-the-shelf template. It’s just a collection of themes and pre-built components — useful for devs who want to get started quickly on a project, but it’s cookie-cutter and can easily be replicated by anyone with Tailwi…
> It’s just a collection of themes and pre-built components
All reusable web components could be described as an optionally themed pre-built component. That's kind of the point.
Re: Vanilla JavaScript support for Tailwind Plus
#37Earlier quoted context omitted.
The title of the blog post mentions Tailwind Plus so I’m assuming it’s a paid feature. The ambiguity is probably intentional.
It's not very expensive, all things considered. $299 for a single-user perpetual license (includes all future updates too) or about $1k for a team license[1]. If it saves you a bunch of time writing and maintaining the sort of components they are showing off, probably worth it? [1] https://tailwindcss.com/plus#pricing
Re: Vanilla JavaScript support for Tailwind Plus
#38Earlier quoted context omitted.
The title of the blog post mentions Tailwind Plus so I’m assuming it’s a paid feature. The ambiguity is probably intentional.
It's not very expensive, all things considered. $299 for a single-user perpetual license (includes all future updates too) or about $1k for a team license[1]. If it saves you a bunch of time writing and maintaining the sort of components they are showing off, probably worth it? [1] https://tailwindcss.com/plus#pricing
Re: Vanilla JavaScript support for Tailwind Plus
#39Re: Vanilla JavaScript support for Tailwind Plus
#40The 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…
Honestly, I kinda feel like 37Signals would have been better off with the founders having someone to report to...