Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vanilla JavaScript support for Tailwind Plus

tailwindcss.com

Post reply on HN
Print view View original

41–50 of 202 posts

Re: Vanilla JavaScript support for Tailwind Plus

#42

Post by moooo99 »

agloe_dreams wrote: post #40
abtinf wrote: 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…

> Kind of like how Jeff Bezos threw a bunch of money at 37signals Honestly, I kinda feel like 37Signals would have been better off with the founders having someone to report to...

How so? As an outsider, they appear to be a healthy business ans a good employer to work for?

Re: Vanilla JavaScript support for Tailwind Plus

#43

Post by richardlblair »

moooo99 wrote: post #42
agloe_dreams wrote: post #40

Earlier quoted context omitted.

> Kind of like how Jeff Bezos threw a bunch of money at 37signals Honestly, I kinda feel like 37Signals would have been better off with the founders having someone to report to...

How so? As an outsider, they appear to be a healthy business ans a good employer to work for?

Didn't see today's DHH rant about talk therapy?

Re: Vanilla JavaScript support for Tailwind Plus

#45

Post by trevorhinesley »

richardlblair wrote: post #43
moooo99 wrote: post #42

Earlier quoted context omitted.

How so? As an outsider, they appear to be a healthy business ans a good employer to work for?

Didn't see today's DHH rant about talk therapy?

Where he encouraged people to lean into intentionality and finding purpose rather than using therapy as a replacement?

I have a diagnosed anxiety disorder and I’ve benefited GREATLY from talk therapy in numerous ways. I’m an advocate for therapy. I simultaneously stand behind his post as a healthy nudge for many.

Re: Vanilla JavaScript support for Tailwind Plus

#48

Post by GenerWork »

dawnerd wrote: post #41
ayhanfuat wrote: post #39

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.

They also had a figma design library that went away. Kinda silly if you want to get designers on the same page.

At this point, the new crop of AI enhanced design tools are basically skipping vector based design and jumping right to code. A lot of them are using ShadCN/UI which is styled using Tailwind, so it's more like designers are somewhat unknowingly getting onto the same page as Tailwind.

Re: Vanilla JavaScript support for Tailwind Plus

#49

Post by bernawil »

notpushkin wrote: post #29
nettlin wrote: post #25

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?).

class soup is what tailwind is. It's terrible because is just abbreviations of css attributes which you still need to know because you'll inevitably fiddle around devtools trying things out.

The only "smart" thing about it is leaning strongly on using rem.

how can it spill out onto the page? it's inline css. The (rare) inline selectors target only descendants.

Truth is that it's winning over because it works best with LLMs. Inline soup works better than looking for styling on different files in the context of the project, so here we are.

Re: Vanilla JavaScript support for Tailwind Plus

#50

Post by nop_slide »

vFunct wrote: post #5

Would this work with DaisyUI components?

I don't see why not. I imagine the css classes in the examples are simply for styling, as long as you nest and structure the custom elements themselves correctly I imagine you should be able to style them as you wish.

I have a daisyui project too, so I might try this later.

Post reply on HN