|
|
|
|
|
by nawgz
1154 days ago
|
|
Indeed, personally I would never open a conversation with that, but I believe this is someone gussying up their personal hobby project where they learned how to use a CSS framework into a "real project" while they denigrate someone else. If we're going to discard some projects as real, a pretty easy filter is "were multiple people required to build it". People who need Tailwind to provide their design system like Tailwind, but they are usually working on very small-scale projects they're unlikely to maintain and upgrade like a project with real users, real design, and multiple engineers would. And a pretty easy proxy for the latter type of shop is "do you have people who aren't even front-end engineers doing your design", and that commenter was displaying all those signals to me. |
|
Do you believe that
The New York Times (2023): https://tailwindcss.com/showcase/nytimes
Shopify (2023): https://tailwindcss.com/showcase/shopify
OpenAI (2023): https://tailwindcss.com/showcase/openai
GitHub (2022): https://tailwindcss.com/showcase/github
The Verge (2022): https://tailwindcss.com/showcase/the-verge
Google (2022): https://tailwindcss.com/showcase/google-io-2022
Microsoft (2022): https://tailwindcss.com/showcase/dotnet
Netflix (2022): https://tailwindcss.com/showcase/netflix
Mashable (2022): https://tailwindcss.com/showcase/mashable
don't have teams with "design chops"?
----
Anecdotally, I can tell you that Tailwind is heavily favored by shiny designery startups. Many of the best designed websites these days are built with Tailwind, and design-oriented engineers are reaching for it first.
Back in 2018 I was arguing against utility classes and vetoing their use in projects I was involved with in favor of thoughtfully architected SCSS. By now in 2023 it's clear Tailwind has earned its place in high-end UI development.