2 ms·
So many of your points are strawmen. > every month new libraries you have to use, always a new framework or cloud service on the horizon, always a new hype in
by schwartzworld 7y ago
So many of your points are strawmen.
> every month new libraries you have to use, always a new framework or cloud service on the horizon, always a new hype in the making
Did your job actually make you switch frameworks or use new libraries every month? Or is this just a trope you're repeating. That's not a problem with JavaScript, but a problem with your management.
And BTW, there are three big frameworks that are all like 5 or 6 years old. React isn't exactly new.
> Think you can still write in the old fashion? Nope, PR declined!
I read posts every day where people talk about JavaScript's horrible language design. Now the language is expanding and solving a lot of those problems, all while maintaining full backwards compatibility, and you're complaining that it changes too often? The last major language update was in 2015, and everything else has been an annual gift of a couple of new features, all of which are developed with the input of the community, and you're still complaining?
The truth is, a lot of people are using JavaScript and it's very flexible, so, yeah, people come up with design patterns all the time. Some of them are good and stick. Some of them are not. But part of the fun of being a JS dev is you can choose to explore that or not.
> JS is deprecated, it's Typescript now!
TypeScript isn't my thing, but again, people are constantly complaining about JavaScript for not having classical language features like strong types. Then an alternative comes out, and is embraced by a large portion of the community, and again with the complaining! Just don't use it! And BTW it seems bizarre to complain about TS being too verbose when you are a C++ dev.
I'm not saying you can't enjoy C++ but your reasons for hating JavaScript just sound like repeated tropes. If you get better at the language (and this applies to TS too), it will stop being so opaque.
- robgibbons 7y agoRespectfully, I think it's unfair to say these are straw points. Perhaps there is some hyperbole in suggesting you need to use every new framework. You really do not. But as devs we are highly encouraged to stay abreast of these sorts of shifts. The industry is always in motion, and modern JS can be particularly brutal. In fact, ECMAScript itself recently moved to a much more rapid release cycle. The market, if not your particular company, requires that you know the latest iterations/tooling of your chosen framework. Even if you're not forced to use the very latest versions, just being aware of all of that movement has cognitive overhead. If you choose not to pay much attention, you can quickly fall behind the curve. There is an inherent anxiety to that reality, whether it's legitimate or not. Multiply the number of different tools in a given stack by the frequency of major updates to each, breaking changes between different tool/plugin versions, and you can start to grasp why people often complain about FE dev. These tropes are repeated for a reason.