Creators of Tailwind laid off 75% of their engineering team
Creators of Tailwind laid off 75% of their engineering team
All subscriptions are for the lifetime of the product, aren’t they? It’s like Plex Pass; pay monthly/yearly or buy the lifetime and hope they don’t bankrupt out. But if you like a product like that, there’s only a few options, and it seems like they’re trying to stay afloat and still make a relatively open product.
And there’s always the free tier for personal use, which seems to have been glossed over.
It’s not particularly bad value for what they’re offering, which seems to be a component library and set of templates.
For a comparison, the company I work for are paying over a £1000 / year for MUI-X, which is a set of paid React components. It’s cheaper and more efficient than paying someone at our company to maintain our own component library.
Even a single engineer spending 10% of their time (as I used to) maintaining this stuff would cost the company over £5000 / year in manpower.
It’s effectively an alternative to plain CSS. Works well with component-based systems like React and Svelte.
I used it for a few years and thought it was pretty good. I still use it on some of my projects.
A CSS framework that moves writing CSS into the html to make it stupidly long with annoyingly confusing class names.
I might be biased though. I hate it.
That sounds too loud, what’s the actual meaning behind what they’re saying? To me, that looks like maybe they hired too many people assuming their business would only grow. That’s the delusion some Silicon Valley folks have, with the sort of VC culture. Perhaps they shouldn’t grow in employees (why are there employees in the first place?) and try to be sustainable instead. The whole project looks so flashy, but does it even need to grow?
On a personal note, I’m not a fan. I used it in a couple of projects, and wasn’t sold on the idea of never ever learning CSS and make your classes not semantic at all. However, I think there might be cases where this approach makes sense. I just haven’t found it so far.
CSS is for StyleSheets (so yes layout and font but also more). Adding these features allows for more reactive/responsive styles where the style may be behaviorally defined instead of hardcoding styles.
Basically the only thing I can think of to do with it is some kind of reactive layout that crunches some data and responds to it. IDK, I’m not a web dev and try to avoid CSS when I can.
Sounds like Tailwind is facing some headwinds.
I’ll see myself out.