Top
Best
New

Posted by kevlened 4 days ago

Creators of Tailwind laid off 75% of their engineering team(github.com)
1451 points | 836 commentspage 10
ZeroConcerns 4 days ago|
That's sad to hear, if true, and I'd have gladly paid for Tailwind if they'd had a "OK, so you use our CSS indirectly" program in place. I'm aware of "Tailwind Plus", but that seems to be React-only, and thus the opposite of where I want to be.
freedomben 4 days ago||
It's not React only. It has pure/regular HTML, React, and Vue. I have mainly only used the pure HTML personally as I use Phoenix/LiveView for most of my stuff, and it works phenomenally well and is very copy/paste friendly. The UI/console they provide is also top notch. For others who do use React, the React stuff also worked well too for one project I did that was a SPA.

It's well worth the money IMHO.

ZeroConcerns 4 days ago||
I just had a more-detailed look, and I'm not sure where I'd find the pure-HTML stuff? From https://tailwindcss.com/plus/templates/pocket#pricing:

"Our website templates are built using Next.js, so all of the markup is written using React"

And the individual components that make up these templates don't seem to have pricing attached, nor non-React usage examples?

freedomben 4 days ago||
Oh, yeah the templates are React/Next.js, but the components and things are not (they are what I described above). Templates are great but 95% of the value I get is the components and things
ZeroConcerns 4 days ago||
So, my initial reaction that "Tailwind Plus" only offers apparent value for React users is... entirely valid?
freedomben 4 days ago||
Only if you ignore this part of my comment:

> 95% of the value I get is the components and things

If you want (and only want) a pre-built site that just needs populated with content and maybe minor tweaks to things, then yeah it's React world. However I've rarely found that any template site (Tailwind or otherwise) is close enough to where it doesn't need medium to major surgery to meet my needs, at which point it's usually faster to just copy together components to what I actually want

ZeroConcerns 4 days ago||
> If you want (and only want) a pre-built site

No, I want to be able to @import "tailwindcss" without feeling guilty.

> I've rarely found that any template site

Well, meet https://basecoatui.com -- and there's more where that came from.

So, ehhm, no, I'm not ignoring the salient part of your comment: you are ignoring the entire point of my post, which is that if Tailwind had a non-React monetization strategy, things maybe, possibly, might have worked out better.

freedomben 4 days ago|||
> No, I want to be able to @import "tailwindcss" without feeling guilty.

tailwindcss is and always has been free, so I don't understand why there would be any guilt with using it. Tailwind UI/Tailwind Plus is essentially pre-built components built using tailwindcss, plus some pre-built site templates.

> Well, meet https://basecoatui.com -- and there's more where that came from.

Thanks, that looks great and will be useful to me! However, unless I'm missing something basecoatui is a component library much like what Tailwind UI/Tailwind Plus provides (though organized differently and useful in a different way IMHO). The template sites are essentially complete websites that you just git clone and it's ready to run. Quite different. basecoatui would be very useful to me, whereas template sites rarely ever have been.

> So, ehhm, no, I'm not ignoring the salient part of your comment: you are ignoring the entire point of my post, which is that if Tailwind had a non-React monetization strategy, things maybe, possibly, might have worked out better.

Apologies if that came off harsh, I didn't mean to ascribe any malice to your reply. However, it seems like there's some confusion here about what the Tailwind "templates" are. They aren't a component library, the component library is different and is not React only.

So to summarize, there are two major parts that are different:

1. Templates (pre-built sites that you git clone). React only

2. Pre-built pieces/components that you copy/paste and modify into your existing app.

whstl 4 days ago|||
You were linking to their React-only offering above, but the actual Tailwind Plus website is this one: https://tailwindcss.com/plus

The Tailwind UI blocks are a similar offering to Basecoat, and are available in non-React format.

The "Tailwind React Templates" are not really similar to Basecoat.

james2doyle 4 days ago||
You can actually use tailwind via the script tag in a plain HTML file. Not for production, but great for whipping up prototypes
freedomben 4 days ago||
Indeed, I've done this quite a few times myself. It's also a phenomenal way to be able to start poking at UI immediately without messing with build pipelines or anything besides just pointing your browser at `file:///...`. Then if the prototype is useful it's very easy to just delete the script tag and get it set up "properly" for a prod build and you know your prototype will pretty much "just work"
deevus 3 days ago||
Sad to hear. I have a Tailwind Plus license (when it was previously Tailwind UI). They are fantastic components and to be honest they keep me writing React even though I would rather not. Catalyst UI is too good.
wg0 4 days ago||
While I'm a shameless freeloader with mostly backend skills - Adam has my utmost respect for out of the box innovation.

I did buy some of this books. Not the Tailwind UI though.

Adam, you gotta pay bills too. I understand that. And I respect that.

The day a product of mine starts making money, I'll come knocking your door.

Thank you.

mjwhansen 4 days ago||
Nothing but love to Adam and the Tailwind team (including now-former team members) today. They’ve made huge contributions to web development and it just sucks, sucks, sucks that things have turned out this way. I know he’ll find a way forward, though.
maxbaines 3 days ago||
I nearly always use Tailwind, had no idea there was even a Plus offering. Checking the site I see it now but it’s a subtle link. Also wonder if shad/cn had something to do with the reduced usage of plus.
robertjpayne 3 days ago|
shadcn/ui I'd argue is probably the single biggest factor in the declining Tailwind revenue more so than just LLMs in general.

As said is it is to say shadcn is what Tailwind should've created and maintained for a fee rather than some html/css templates that are easily replicated.

I say this as someone who bought Tailwind+ to support the project many years ago and still use Tailwind every single day.

waynesonfire 4 days ago||
Maybe you don't need a massive engineer team developing Tailwind and "monetizing it" You, Tailwind, don't get to collect ALL the rent. You were made "successful" because you created something that was OPEN SOURCE and the community chose to adopt your technology because of that. You wouldn't even exist had you not had the foundation, made the implicit statement that, I am willing to share rent by open-sourcing. You wouldn't even have ONE engineer!! You're now crying because you over-sold your success and improperly scaled your business. Your fault. IF all you need is two engineers that's fine. That's your piece of the rent. Other business are hiring far more than the 75% you laid off and building and creating value on top this open source technology. No jobs lost, just your ego and the empty promises you made to investors.
moralestapia 4 days ago|
[flagged]
bakigul 3 days ago||
If the business model had evolved together with artificial intelligence, we wouldn’t be talking about a 75% layoff today we might be talking about a 75% hiring spree instead.
another_twist 4 days ago||
Where's the 75% layoff number from ? This thread is about making docs llm friendly.
magician2229 4 days ago||
I listened to his podcast this morning where he mentions 75% of their four person engineering team was laid off (only the founders and one engineer remain)

https://adams-morning-walk.transistor.fm/episodes/we-had-six...

bakies 4 days ago||
75% is a lot more dramatic than 3 people geez
tacker2000 4 days ago|||
Yea this feels kind of unecessary from him and makes him look a bit full of himself.
ZephyrBlu 4 days ago||||
He said he wanted to state it like that because he thought just saying "3 people" undersold the impact.
8note 4 days ago||
the impact of which seems a lot like its changing from company into side-project
system2 4 days ago|||
Welcome to the age of clickbait and fake drama.
arccy 4 days ago|||
if you actually read the thread: https://github.com/tailwindlabs/tailwindcss.com/pull/2388#is...
another_twist 4 days ago||
Missed this bit, thank you.
mucha 4 days ago|||
Adam added a comment to that thread with the 75% number and more context.
sumedh 4 days ago|||
Scroll down
zeroonetwothree 4 days ago||
ctrl+F 75%
websku 3 days ago||
I've seen that the team had 4 members. 3 being laid off.
novoreorx 3 days ago|
> And every second I spend trying to do fun free things for the community like this is a second I'm not spending trying to turn the business around and make sure the people who are still here are getting their paychecks every month.

Man, you can really feel the anxiety and desperation in Adam's reply.

Part of me wants to say "look what evil VC money does to devs", but that's only a harsh critism of a bystander.

Monetization is a normal path that the successful OSS projects would take. Tailwind went big on the startup route, took a bunch of VC cash a couple of years back, but despite the massive impact on the dev world, they clearly didn't hit the revenue numbers investors expected. Now the valuation bubble popped, and they're forced into massive layoffs. Though to be fair, maintaining a CSS library probably doesn't require that many people anyway.

I really feel for Adam here. He didn't really do anything wrong. Eagering to build a startup after your project blows up is a totally natural ambition. But funding brings risks. Taking other people's money makes you go from being the owner to just another employee real quick. And once you hop on that VC train, you don't really call the shots anymore. Sometimes you can't stop raising or scaling as your own will.

If you find a solid business model, that's great. But if not, well, honestly, a 75% layoff is getting off lightly. At least they still have a chance to keep on.

But he obviously didn't foresee this coming. He’s getting torn between being an OSS maintainer and a CEO who have to be responsible for stackholders and employees. That internal conflict must be brutal. It’s pretty obvious he didn't reject the PR for technical reasons. It's just because the reality hit him hard, and he has to respond to it, even if it goes against his mind as a developer.

Really hope Tailwind pulls through this. Also, this is a lesson worth noting for the rest of us. As indie devs, if you ever get the chance to take VC money, you really gotta think hard about whether you're truly ready for the strings that come attached.

More comments...