How is this different from tachyons?
No built in breakpoints, or any direct ui manipulation leaves you with a cleaner starting point. Of course it depends on the use case; in ui-heavy projects I'd like to control the bits.
Also, it is smaller, more literal, and was useful for me before, that's why I made it public.
Wow, this is pretty cool! My team uses tachyons in large production systems, so it's nice to see similar approaches coming up.
I actually think Tachyons is too large to be used in some contexts — for example, when I need to do a small change or addition to an existing service, but don't want to mess with the (terrible) legacy CSS that's in there.
Glad to see fractures as it seems like the perfect toolkit for these situations, where I need in-n-out atomic CSS.
Tachyons allows you to import the specific module you need from it, so you can avoid the whole library.
At the bottom of this example component page are the individual modules needed to create it: http://tachyons.io/components/article-lists/title-preview-author-media-flipped/index.html
Also helpful when importing via NPM in a JS project. You can pull in just the CSS rules you need.