cs-what VS twin.macro

They say that if you try it you wont go back. But we know a lot of people who got to a certain place in a project and wished they could. But we might never know - because we have our own stubborn ways of doing things - and we're sticking to them! ;)

I've been working on a new CSS framework that you might like: https://github.com/perpetual-education/cs-what

I still think that Bootstrap and Tailwind are a bit backward. May as well go all in and use CS-what. I'd personally never sign on to a project that forced me to use them but I'm spoiled. My job is to teach how to write great HTML and CSS. But that doesn't mean that utility/class frameworks don't have value to other organizations. Their goal is to make it easier and more maintainable, so - if you learn CSS well, then you should we able to be productive in a framework right away. Any CSS lover has at some time created their own little framework (or many) along these lines. And there's no silver bullet. But the problem with that is - then the other team members will have to learn your unique angle on CSS.

After reading this thread, I created a new CSS framework that will help everyone skip learning CSS. https://github.com/perpetual-education/cs-what/blob/main/README.md

Twin Macro Github Repo. This is a great resource to help you pick up Twin’s syntax, learn more about the package, and keep up to date with the latest releases.

Personally I like twin.macro the most. It’s similar to the above but based on Tailwind.

twin.macro is a library that allows you to use these styles in your JavaScript code. This library works exactly like styled-components.

One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:

twin.macro

If you use Tailwind with React a lot, and are wanting support for Styled Components, give Twin Macro a look. They're close to finishing support for TW v3 in their Releases section :)

The blocker for us using it is our use of an excellent library called twin.macro which is built against babel's transpilation APIs to parse tailwindcss directives at compile time so that they may be used with css-in-js libraries. This efficiently bundles your css so that you only ship the precise css you use. The problem is, it's all quite slow.