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.
-
-
my inline styles turn into css. does that change anything?
@rauchg -
good convo. probably worth continuing in various forms via continued real-world exploration. Keep on keeping on!
-
to me, it matters little how it's written as long as maintenance is taken into account. Both can be nice.
-
this is my priority as well

-
I wrote about this a month or so ago: https://www.google.com/amp/s/css-tricks.com/on-style-maintenance/amp/?client=safari …
-
/me reads
-
stream of consciousness: I think your OO/FP division is too charitable to FP.
-
yeah, like every other developer I have my preferences ;)
- 4 more replies
New conversation -
-
-
this seems like an argument for avoiding canvas… CSS in JS syntax shouldn't change any of those properties
-
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.
- 4 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.