Hype considered harmful
Yep, another «XX considered harmful» clickbait title.
So. This thing happened:
A big advantage of CSS in JS(X): One language (JS), not three (JS, HTML, CSS).— Guillermo Rauch (@rauchg) 26 novembre 2016
One linter. One code style. One type system. One test system.
I quoted the things saying:
MAKE FRONTEND GREAT AGAIN #WebmasterGate #CSSFTW
Then, Freddy replied:
Maybe you should stop complaining about the hype, the js fatigue and at the same time the proposed solutions, no ?
It is exciting and exhausting at the same time.
Exhausting because you will always spend too much time on the tooling and trying to impose the latest framework or library. Since it is moving so fast, it is not the time to do everything one way thinking it is the only way. You have to think before choosing a stack for your team, your project, and think even more before pushing your shit into production.
A communication from a not so far future:
- Full bloated frameworks sucks ! - Yep, we're so much better with half a dozen libraries - Sure, but I'm not always sure how to connect things up. - Don't worry, use this boilerplate. (later) - Full bloated boilerplates sucks !
The hype is dangerous, use it with care. I will never stop saying that.
I wrote an article before ES7 was out about the ES7 fatigue. Guess what: async/await are still not finished. U mad ?
About the solutions
- One linter: have you tried playing with JSX and jshint ? Not everybody uses ESLint, and that is a good thing.
Also, CSS has a type system for values:
Then, how do you manage the learning curve ?
I am sure you encountered this article, newbies will surely feel the same. When you impose the stack Guillermo suggests, you close the door to a lot of people because there is too much to handle.
With all these things you have to learn, you will end up mastering nothing.
- Am I complaining about the hype ? Yes, because I think it will hurt many teams and projects.
- Am I complaining about the solutions ? Yes, because I think they are not viable solutions on the long term.
So no, I will not stop. Sorry.
I’ll add some more:
- Should I stay with a legacy stack forever ? No.
- Should I stop learning new things ? No.
- Should I stop sharing them ? No.
- Should I follow all the things I read on Medium ? No.
- Should I think before choosing a stack for my project ? Yes.