Facebook’s Tailwind Killer Is Now Open Source
Facebook recently announced that they have open sourced the code for their internal tool, which they have dubbed as the “Tailwind Killer.” This move has garnered a lot of attention within the web development community, as it has the potential to revolutionize the way developers approach building and styling their web applications.
The “Tailwind Killer” is a utility-first CSS framework, similar to Tailwind CSS, which has gained popularity for its approach to building customizable and responsive user interfaces. However, Facebook’s tool claims to address some of the pain points and limitations that developers have experienced with existing frameworks.
With the code now available as open source, developers have the opportunity to explore and contribute to the tool, and potentially incorporate it into their own projects. This move by Facebook demonstrates their commitment to supporting the open source community, and their willingness to collaborate with the wider developer community to advance web development practices.
According to the announcement, the “Tailwind Killer” promises to offer a more efficient and scalable approach to writing CSS, while providing a high degree of customization and control over the styling of web applications. It aims to simplify the process of styling user interfaces, and enable developers to create consistent and visually appealing designs with minimal effort.
As open source, the “Tailwind Killer” will likely attract a community of contributors who will work together to enhance and expand its capabilities. This collaborative effort has the potential to drive innovations in web development and contribute to the evolution of best practices in styling and building user interfaces.
With Facebook’s decision to open source their “Tailwind Killer,” the web development community can look forward to exploring and leveraging this tool to improve their development workflow and create more polished and engaging web applications.
Overall, the release of the “Tailwind Killer” as open source represents a significant step forward for the web development community, and underscores the importance of collaboration and sharing within the industry.
css is so simple…why the hell would you change that with stylex or tailwind? so you could have insanely complex or insanely bloated classes?
Why is the React community still trying to solve solutions most other frameworks solved years ago? Vue, Angular and Svelte has had scoped styles with colocation and conditionals from the get go. The only thing interesting here is specificity but that is extremely rarely a problem when you create small components.
what ??? really !!! the implementation is completely terrible i cannot use stylex and add code css with this syntax, it s more complicated and not very clear and clean.
Lol how's it any different from styled components?😂😅
this is the react dev team in a nutshell "There are benefits of DRY code, but we don't think"
How is this different from any other css-in-js solution? Three major concerns with stylex:
❌ come up with your own classnames (yes they're scoped, but still)
❌ your styles are no longer in your component (they are declared outside now, and sharing fully gives up co-location)
❌ come up with your own design tokens (this is a major PITA, and Tailwind provides design tokens for spacing, border radius, shadow, colors, etc)
No thanks.
Nah, not interesting enough. Meh.
Immediately said NOPE when looking at it. It still separates the styles from the actual elements, still using JS syntax instead of simply classes(stop mixing things!). Passing styles as props? Please no. This is just overcomplicating things
Another stupid CSS framework. Facebook is a king of hype
#googleconsolecreator®©
These "Killer things" are so stupid…
Oh no. My brain hurts. I've decided to stop learning anything new.
I mostly like the the T3 stack for quick development but the adoption of Tailwind has always been the one thing I’ve never understood. It’s inline styles using themed utility classes right? But it completely obscures the CSS industry standard, requiring new naming for everything and a lookup table to get anything done. I like inline styles using the styles prop in React because they are right there as you develop and read code, is fully customizable and easy to understand by anyone familiar with CSS. It’s even reusable if you want since it’s all just objects. Stylex appears to build on that concept adding support for some sudo class functionality too. IMO this is how I’d recommend small teams to work. For larger orgs wanting consistent styling I’d recommend a component library instead.
It’s also worth noting that when both of these libraries lose popularity in 5-10 years, only the skills of one of these 2 tools will transfer over (unless css is gonna go by the wayside entirely which is very unlikely)
SCSS Modules is still the unofficial king for me, clean css classnames and little to no worry for conflicting names. People should learn to write real css classes, much more portable than if you were to use tailwind for example, and had to port.
For instance, lets take Header.module.scss as an example:
* Has the power of SASS
* Ensures no className collisions
* Doesn't convolute your CSS with terrible backtick-JS-in-CSS which just looks plain ugly
* Oh and the few guys in your team who love and breathe CSS will be happy to actually have CSS files that every IDE knows how to deal with
* It keeps your files more specialized, not a mixed bag of HTML, JavaScript, and CSS. CSS does not belong in my JavaScript code.
I don't see how this is any better than tailwind + cva/tailwind-variants. With cva or tailwind-variants you can separate the styling part and still co-locate. Regarding typesafity, having tailwind intellisens extenstion is sufficient.
If this would have existed pre tailwind, I would likely have considered it tho.
Style𝕏
this looks like makeStyles from mui which was quite a cancer, never again..
UNO CSS!!!!
This is worst than tailwind shit😂
I don't believe that creating all these abstractions are necessary for styles. And.. what's not scalable about a ui component libarary? This defines a much more clear boundary between teams because the implementation details of how to apply styles don't have to be shared. I think meta is not moving in a direction where they improve web standards. I think they are even making it worse by introducing all these weird mental models around otherwise simple applications. I don't look forward to having to think of a million definitions of styles in other files, and to not using highly optimised css stylesheets.