Lessons learned at React Amsterdam

I think it’s great to share your learnings with the community. I can’t say I agree with some of them like — inline styles. being —

  • CSS in JS is not only for big projects, it’s for any maintainable project.

This is quite a bold statement and I don’t believe you can prove it’s going to help for maintainability.

  • Separation of concerns is good for maintainability.
  • Organised, consistent code is good for maintainability.
  • DRY (Don’t repeat yourself) is good for maintainability.
  • Resource management of peoples skills is also fundamental to maintainability, because who is going to maintain it?

Mixing css in javascript breaks the above.

External css in one folder, perhaps named according to the components is a clearer separation of concerns.

Css classes can be named and developed in a way so as not to have to be repeated for every render of that component.

Designers, and html/css specialists who aren’t good at javascript are better at styling than javascripters doing everything and having to keep up with the curve of so much new technology — react/jsx/es6/redux and so forth. They will know where to go and edit the css if it’s external.

There is a big community of newer younger javascript developers lacking experience on the front line of styling / branding, accessibility, semantic structure, micro data and so forth. They will be hungry to develop the behaviour, the interaction between the data coming through and the user interface. They will charge a certain fee for their new experience in this competitive market and companies won’t be able to afford react developers to do css specific work, and many aspects of good css management will become un-maintained.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.