|
|
|
|
|
by 5zBFyURxgY
3225 days ago
|
|
Just don't do it. I totally regret I went for Javascript. I started with systems programming with C++ etc.. At some point some 5 years ago I made the unfortunate decision to go for Javascript. After 5 years I can now confidently say that programming in Javascript is not about what you are creating, it is about what ESxxx version you use, what framework you use, whether you're using Promises or whatever idea people come up with tomorrow, and all this in an ever accellerating and continuing hype. I am sick of it already. Almost everything I learn is already, or will be soon, deprecated. I would recommend people to go for C++/Qt or any language/framework where what you learn will not be wasted soon so you can use your valuable time to create things rather than learn the next framework or language idea all the time. |
|
I dumped node.js on the server site like a hot potato. At the time (2014), it didn't scale well and was quite porous dealing with stuff you'd get free in a framework like django (like db-backed form validation).
But, I can't say I regret learning JS. You won't be able to do the job developing websites if you can't wrangle it. It's so ubiquitous, despite my efforts to keep a node-free codebase, I still had to cave in. Even if it's just getting your foot in the door using SCSS. Or wiring in that jQuery plugin.
Whether it's situational awareness or dealing with webpack configurations, getting that last 10% cinched is going to require understanding what's going on.
What I think people need to know about JS is that they shouldn't just drink the Kool Aid because everyone else seems to.