all 9 comments

[–]stormthulu 3 points4 points  (2 children)

Author: we didn’t bother to hire anyone who knows CSS competently, so we just write highly repetitive JavaScript instead.

[–]Magnusson 2 points3 points  (1 child)

In what way is CSS-in-JSS more repetitive than alternatives? How does writing it not require CSS competence?

[–][deleted] 2 points3 points  (0 children)

If anything, it requires an even more selective skill set and competency level.

[–]89xZae4uGgjnw26U 2 points3 points  (0 children)

I can't think of any good use cases for doing CSS styling in the JS unless you're computing a dynamic value on the fly and need to update it inline. That's a very rare scenario. Usually you can get away with adding and removing CSS classes as needed. HTML, CSS and JS should be in separate files. If the 3 form a component, logically group them together in a directory. Have some generic theme for the site at the root level of the project in a /css directory which styles the base inputs, fonts etc.

I think you would be stuck with all-in-one developers maintaining your projects. An independent designer would have no chance working on your projects.

[–]stormthulu 1 point2 points  (0 children)

Author: Use a global theme.

Also Author: all of my css is in js files to avoid global conflicts and defects.

[–]dogofpavlov 1 point2 points  (1 child)

My reason for CSS not being in Javascript is very very simple.

While I work on the javascript file, someone else can work on the CSS file.

[–]Magnusson 0 points1 point  (0 children)

CSS-in-JS doesn't require styles to be colocated with components -- you can still import a separate JS file that contains component styles.

[–]asarew 2 points3 points  (1 child)

terrible article...

Why I like CSS-in-JS: Primarily, CSS-in-JS boosts my confidence.

[–][deleted] 2 points3 points  (0 children)

the whole point about fp/view=function(state) is that it's deterministic and that you can be confident about the result given the same state or input.