Internet is drunk!
I believe this whole direction is rooted in laziness to learn CSS.
CSS pre-processors and command-line coding is not only cool but very effective when done right. SASS mixin parameters with the combination of tools like Gulp made web development really fast and nice. Automation is great!
But it flipped overboard and this article by Cole Peters is great: On writing real CSS (again)
Setting up a workflow with CSS pre-processors and command-line tools takes time and commitment to the technology powering those tools.
Looking at it, it seems as back-end developers, forced to do front-end development, figured out a way to make front-end development as advanced as back-end development.
Let's talk about ReactJS, it's a framework much like AngularJS promoting writing code that honor said framework above common web standards and rules. To be fair most frameworks do this. ReactJS is promoting inline coding. Meaning instead of keeping logic and GUI separated it combines it.
The Debate Around “Do We Even Need CSS Anymore?” http://t.co/IAJpRJNBEz— CSS-Tricks (@Real_CSS_Tricks) June 26, 2015
An Example: While I utilize inline CSS in occasions where an element won't be repeated manually again, it however means I can let my favorite CMS or Programming Language repeat that element as long as I only have to edit the inline code in ONE PLACE.
The whole point of NOT using inline code is we want 1. Separation and 2. GLOBAL control! MVC/OOP aside I can't imagine or grasp a website where there isn't an overall stylesheet and everything is being coded inline. // I suspect Facebook will soon have 16,000 different styled elements :D
I am not against change. I read about Rachel Andrews CSS Grid Layout with great excitement and I got tempted to learn Ruby on rails after watching this presentation: A Maintainable Style Guide But once again:
"A common question has been how do we handle CSS and JS related to these components. Unfortunately I don't have a clever answer for this at the moment, it's a mostly manual process."
Eric Elliott makes the case that the inline coding happens in components and as of such only needs to be edited in one place.
He says "React is all about separation of concerns." I read: "React adds a new layer of logic and style to huge websites where developers have lost control over CSS and let it grow to unmanagable sizes." Am I reading it wrong?
I often hear claims that “the DOM is slow!” and “React is fast!”, so I decided to put that to the test: https://t.co/M1RZZiyVT2 🐢vs🐇— Paul Lewis (@aerotwist) July 3, 2015
12 years of progress? pic.twitter.com/uOQ7ine7LV— Sam Stephenson (@sstephenson) May 10, 2016
"Basically, both Google and Facebook are desperate to find a baseball cap that they can put on backwards. Angular is Google's baseball cap. React is Facebook's."
Take a shower, get sober and go learn some REAL CSS - while taking a break from CSS pre-processors!
Remove unused CSS https://t.co/INVKicyuqt— Florian Voutzinos (@voutzinos) June 24, 2015