HTML and CSS are not a separation of concerns in anything I've ever built. They're both representing the layout/design. I don't want them separate. You end up having to keep them synchronized anyway, messing with your HTML is frequently gonna break your CSS. Tailwind is infinitely more pleasant to write than a separate CSS file that has to be kept in sync with the HTML.
dude, have you heard about single file components where you have HTML & CSS in one place? XD
Never preferred tailwind. Much simpler to write plain css. It’s easier to create reusable components than what ppl think. CSS hardly has a steep learning curve. Problem with tailwind and many newer css frameworks I see posted even on HN, is they don’t seem to work on older devices, which is a shame. I guess ppl simply test on their latest phones and call it a day. Older ios itself have roughly 7% market share [1], th…
Weird acq but okay Mr Lutke is kinda weird lately in Canada. Wonder why the tailwind guys are getting involved with him
This is hardly surprising after the recent string of venture-backed developer tooling acquisitions: Bun -> Anthropic, VoidZero (vite) -> Cloudflare, Astral (uv, ruff) -> OpenAI
The only thing that remains to be seen is how these affect those tools going forward (and who's next)
(1) Shop Pay is one of the services that I’ve seen grow fastest in market share ever. Like in the last six months it seems like almost every independent online store sees my phone number and offers me a text to pay via shop. (2) Tailwind is part of the CSSSlop ecosystem that includes of course the original Bootstrap, SASS, Emotion and many similar things that never really worked from an ecosystem perspective because…
Components as in React, Vue, etc requires a complete overhaul in frontend rendering, many dependencies, changes in deployment and even have an impact in organizational structure. If one wants to do server side rendering with HTML templates like the old days there is no real “components” way of doing it (although declarative Shadow DOM is coming along). Partials are not the same thing. In that scenario some repetition…
Have you tried Astro? It lets you do exactly that: server-side rendering with HTML templates in component form, with css scoped to the component. No shadow dom needed, no JS frameworks either.
Astro is still fundamentally different, it's not server-side rendered in the sense of dynamic pages. I can't, in a language agnostic way, use Astro to receive a request, get data from the database and render an HTML representation of this data. This won't work in a Go, Rust, or whatever server. Astro at a minimum requires its own compiler to build the static assets, a server to serve them, and a custom API to answer the calls so it can build the dynamic part of pages.
Yeah, Tailwind is great as long as you have some way to reuse markup, like React. You don't have to care about class names and whether CSS defined somewhere else affects styles of a current component at all. That last point makes sense for LLMs as well: all the styles that affect the current file are automatically in context since styling is local. Admittedly, there are other ways to achieve this but the ergonomics o…
The lack of single-file components is one of several reasons I wouldn't reach for React prior to the LLM craze[0]. For personal projects, I love Svelte. You wouldn't need tailwind there for the reasons proposed given their support for it. [0] Things have probably changed, but Svelte 5 was a litmus test for how recent the data cutoff was for an LLM model. Meanwhile React _especially_ has no reason to change how the fr…
You wouldn't need tailwind for svelte, but I've been using tailwind with svelte at work for years now and really like it
"nor should it be" is connected to "being worth millions". It's not that it isn't worth money, but it's more of a lifestyle business than the sort of thing that will drive a tech company with employees, marketing, and conference budgets.
There are several graphing libraries that have been businesses for years. Like Highcharts. A frontend framework used by millions and millions certainly has some value to loads of people.
"The market can stay irrational longer than you can stay solvent" applies to running a business as well as trading. There is no certainty when you're dealing with the individual whims of millions of people.
> the site docs garnering traffic (beyond potential tailwind labs conversions) is more of an indicator of a code or design smell than anything I've heard this before, but it's really no different than vanilla CSS. My guess is that people started pointing this out is that Tailwind got more non-frontend people digging into styling more where they were hit with how much shit there is in CSS.
> it's really no different than vanilla CSS Is this supposed to be a plus? When you have indirections they're supposed to provide some abstraction and the abstraction might or might not provide the utilities you desire, but there is a point to it. A near 1:1 mapping is completely useless and just a different syntax for the sake of it.