A big advantage of CSS in JS(X): One language (JS), not three (JS, HTML, CSS). One linter. One code style. One type system. One test system.
it depends on details. I think CSS-in-JS is a wash for layout but net-negative across the board for content.
-
-
I don't follow, if you accept a build system, how is manipulating the inline style object or injecting generated stylesheets bad?
-
I definitely don't think it's elegant to add such complexity, but maintaining CSS that works in today's browsers is a nightmare
-
there are other choices. I predict that by the end of 2017 the "leading edge" will look very moment-in-time.
-
I'd like to hear about other choices for maintainable CSS, everything I've seen is either BEM-like or still very JS-centric
-
I like a pared down Shadow DOM with good conventions for linking to component systems.
-
can shadow dom be reasonably polyfilled? Native support for it still seems really low.
-
it's hard, but you can probably use a much less annoying BEM + framework help to do something very similar.
-
we have been doing something along those lines, it is very easy to screw the CSS up and can generate a ton of silly class names
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.