Not sure how to feel about this, I hope Shopify will leave the Tailwind team alone for the most part and let them continue what they've been doing.
Shopify acquires Tailwind
31–40 of 388 posts
Re: Shopify acquires Tailwind
#32Here's some context on the impact AI had on the Tailwind Labs business model from January: https://github.com/tailwindlabs/tailwindcss.com/pull/2388#is... > But the reality is that 75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business. [...] > Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever.…
Oof. It’s so sad when businesses with in-demand products suffer from a lack of successful economic mechanism design.
Re: Shopify acquires Tailwind
#33Ugh. I remember how much Tailwind Labs has struggled for funding and it sucks to see Shopify get them. It also sucks to see they're discontinuing their paid products permanently, effective immediately -- they're not making them free, they're taking them away. You simply can't get them now. I understand why this had to happen but it is sad to see.
Why does it suck that shopify got them? They seem to be a good steward of open source, especially with rails.
Usually when stuff like this happens, it means that Tailwind's developers are moving to work on Shopify instead, which means Tailwind CSS itself goes into maintenance mode. That's what usually happens when a dependency is picked up by a company with a huge, "more interesting" product -- the dependency starts to depend on the more interesting product for attention, and stops receiving attention on its own merits. It grows only to support the more interesting product.
Furthermore, I already have specific experience with Tailwind Labs neglecting their other libraries that aren't Tailwind CSS itself, probably because they were only meant to support their paid products (which now will no longer exist! so maybe those other libraries will just stop getting updates altogether). Headless UI was something I wanted to rely on heavily, but it's not built to be flexible enough and basic issues from 2021 or earlier haven't been resolved or seemingly even reviewed.
Now that they have Shopify, I'll be surprised if Tailwind CSS continues to receive any more attention than Headless UI did all those years ago. This acquisition puts Tailwind CSS in exactly that position.
(Edited to fix "Spotify" typos...)
Re: Shopify acquires Tailwind
#34The most pertinent part for many: > On the commercial side, we'll no longer be trying to grow the business around Tailwind. All existing customers will of course maintain their access to products like Tailwind Plus and ui.sh, but we're closing sign ups for new customers to focus on Tailwind CSS at Shopify.
> All existing customers will of course maintain their access to products like Tailwind Plus and ui.sh, but we're closing sign ups for new customers to focus on Tailwind CSS at Shopify.
You've got to wonder how long that model can continue if no new customers are allowed in.
They've even removed the Plus splash page so clicking Plus on the homepage or going to /plus takes you to a login page with no detail about what it was.
Re: Shopify acquires Tailwind
#35AI and Tailwind-based template systems sort of stole Tailwind's lunch, so I'm glad there was light at the end of the tunnel for Adam and co.
Re: Shopify acquires Tailwind
#36As someone who built their entire platform on Tailwind and has been running gpt-6-astra for the last 5 days straight working on the migration away from it because it leaves an irrecoverable pile of slop when your project becomes large enough... Heed my warning.
It's not that Tailwind itself is bad. It's good. But agents are notorious for re-inventing the wheel without hard constraints that prevent them from doing it - and when I say hard constraints, I don't just mean an AGENTS.md file or a skill they can ignore. As such, I found that design consistency was near impossible and a constant firefight. It worked at first, but when my project got sufficiently large, it became worse and worse.
I initially tried combatting this with a spaghetti-soup of linter rules, but it wasn't very effective to maintain. So I'm biting the bullet and moving on to greener pastures.
Re: Shopify acquires Tailwind
#37Very glad they got their exit. Provided huge value for years
Re: Shopify acquires Tailwind
#38meh fuck shopify
Re: Shopify acquires Tailwind
#39Here's some context on the impact AI had on the Tailwind Labs business model from January: https://github.com/tailwindlabs/tailwindcss.com/pull/2388#is... > But the reality is that 75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business. [...] > Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever.…
I think maybe they should have kept building Tailwinds CSS, release new versions, then charge a subscription to teams for their agents to access latest changes in their documents. In other words, the documents for the latest versions are hidden behind a pay wall.
If you release new versions without documentation it's easy for agents to generate that missing documentation.
Re: Shopify acquires Tailwind
#40Happy for Adam and his team.