[dead]
Shopify acquires Tailwind
451–460 of 464 posts
Re: Shopify acquires Tailwind
#452Earlier quoted context omitted.
This is such a poor comment. It starts talking about the business model, but it’s just a “Tailwind shouldn’t exist at all” argument. Clearly it’s a useful tool if it’s used by so many people and companies.
>Clearly it’s a useful tool if it’s used by so many people and companies. Yeah but its not. Hence the huge layoffs. If they don’t want to find another software development job maybe they could work at a New Jersey gas station. New Jersey protects their gas station attendants.
When the layoffs happened they said tailwind usage was way up. Just the paid products weren't getting used.
Re: Shopify acquires Tailwind
#453Earlier quoted context omitted.
You have to remember the biggest appeal of tailwind is that it throws away the entire cascade of css. The people that reach for it are choosing it because it offers less functionality, and is therefore simpler to reason about. I hesitate to say they don't understand css, I'm sure some of them do, but in my experience the devs that reach for it are the same who deride css and make statements such as "I have better thi…
I think there's plenty of developers that are perfectly competent with CSS who still reach for Tailwind. You're right that Tailwind throws away the cascade, or at least enables developers not to have to think about it (under the hood, Tailwind 4 uses pretty modern cascading features like layers), but people aren't reaching it because of a lack of understanding, they're reaching for it because as front-ends get increa…
I'm perfectly competent at CSS and... at this point I don't even look at CSS. I just feed descriptions of what I want to the LLM and it nails it every time. The result either looks the way I want or it doesn't.
I'm not universally pro-AI. I meticulously review every line of backend code, and still do hand edits. I review FE commits less carefully but still keep an eye on it to make sure AI doesn't go off the rails. But there's only so much trouble you can get into with CSS and the problems are the kind of bite-sized problems that LLMs excel at.
I don't think it matters at this point what you use for styling. If you like tailwind, the AIs use it just fine. If you like SASS, or raw CSS, the AIs are also just fine.
I'm not sure there's really a human job here anymore.
Re: Shopify acquires Tailwind
#454Earlier quoted context omitted.
Given how hard it is to build any form of financially sustainable model around an open source project I think we should actively celebrate anyone who manages to build a model that works, not dismiss it as a "gravy train".
I really just think they got lucky, I don't see anything to celebrate. It's like celebrating one of your friends winning the lottery - good for them, but it's not really an indication the system is working well at all.
9 years of work to "get lucky".
Re: Shopify acquires Tailwind
#455Oh, bejesus. Shopify awards the Stupefiers. Why would anyone need any kind of framework for CSS?! It's the inherent human need to control something, to package water and sell it as magical water. I've never understood the whole idea. Bootstrap: the hard-to-remember, horrible shitshow forced on frontend devs. And people thought there couldn't possibly be anything lower than that. Then Tailwind arrived. Apparently, fro…
These are the same anti-Tailwind arguments that have been circulating forever. If you want to build a case against Tailwind that's actually compelling, you should start by understanding what it is first. Only then can you compare it to other frameworks and methodologies.
Maybe you should come up with an example instead of trying to sound wise, while in reality protecting an inferior and useless thing forced on devs.
Re: Shopify acquires Tailwind
#456Oh, bejesus. Shopify awards the Stupefiers. Why would anyone need any kind of framework for CSS?! It's the inherent human need to control something, to package water and sell it as magical water. I've never understood the whole idea. Bootstrap: the hard-to-remember, horrible shitshow forced on frontend devs. And people thought there couldn't possibly be anything lower than that. Then Tailwind arrived. Apparently, fro…
I've made arguments like this in the past, and my position hasn't changed much https://pdx.su/blog/2023-07-26-tailwind-and-the-death-of-cra...
High five!
Re: Shopify acquires Tailwind
#457Earlier quoted context omitted.
> Even Adam admitted that AI impacted dramatically their business. Even the bossman admitted that AI fired his employees, not the boss. I guess that’s why people talk so much about leadership this leadership that. I’m learning that leadership is when you are the captain of the ship and the ship goes down you man the lifeboat and mourn your sailors over what the Sea did to them.
In this specific case (Tailwind Labs) I don't understand this sentiment at all . It was a completely bootstrapped company! Its entire existence is due to the many years of difficult work by its founders. What exact outcome would correctly align with "good leadership" in your view? It sounds like you think the CEO/cofounder should have "gone down with the ship" here -- how does that help anyone if it means the entire…
The last paragraph was a general extrapolation. Strike it from the record then.
Re: Shopify acquires Tailwind
#458Earlier quoted context omitted.
I still think the only reason to use jQuery is if you need IE11 support. Otherwise, it's really simple to do all the things you mentioned without the complexity/heaviness of jQuery. Something like this: ``` const $ = s => { const r = {}; const els = [...document.querySelectorAll(s)]; r.text = t => (els.forEach(e => e.textContent = t), r); r.on = (ev, fn) => (els.forEach(e => e.addEventListener(ev, fn)), r); // ... re…
Does anyone actually need IE11 support in 2026? It was released 13 years ago.
I worked at an enterprise in 2022 that still relied on IE11 in certain places
Re: Shopify acquires Tailwind
#459Earlier quoted context omitted.
> do LLMs change the calculus for DRY? Yes it makes it insanely easy to refactor duplicated logic into shared and tested modules. Why would you go the other way?
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…
What about Phoenix live view?
Re: Shopify acquires Tailwind
#460Never 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…
Why wouldn't Tailwind work on older devices? It's just a bunch of classes. If you're using a feature the browser doesn't support it's not going to work whether it's vanilla css or tailwindcss. That said, I prefer vanilla CSS. Modern CSS is great.
Here is the tailwind website itself - https://ibb.co/album/kHqGx8
This is on iOS 13.6
I have no idea why tailwind needs or does something which makes it utterly unusable. I miss the days when many websites used to offer simple html versions of their apps, like gmail (https://techcrunch.com/2024/02/22/google-is-killing-gmails-b...)