3 ms·

I wish I fully understand what people mean by javascript fatigue. I can translate fatigue to my language, but it still doesn't make sense.

cwbrandsma 10y ago
Fatigue can be translated to "feeling worn out and overwhelmed". Basically, so much change you feel obligated to keep up with that you want to quit. I feel this a bit, there was a time when I could keep up with the changes going on in Javascript, but was overwhelmed by the changes happening in C# and Java (which for a time were going fast and furious). Now I'm ok with C# and Java...but Javascript is going berserk. It comes and goes.
Qwertystop 10y ago
New frameworks keep being made, becoming extremely popular, and then being dropped for the next new framework despite that they often do basically the same thing in roughly the same way. Some people are getting tired of this.
finchisko 10y ago
Thank you guys for explanation. I had feeling that it must be the thing you've described, but was not sure. I was missing js fatigue of what (context). To give example: js fatigue of new frameworks, js fatigue of constant changes... Anyway now I understand. PS: I don't feel js fatigue of any kind and actually like the pace js is progressing. I just don't jump on hype train anymore. Rather wait till things settle and prove their existence.
dexwiz 10y ago
The fatigue comes from having to constantly keep up with JavaScript and everything new. 5 years ago building JavaScript page was straight forward. Most of the time you would include JQuery from a CDN, and code in a server side template. If you were really serious, you used something like Backbone Or Ember (both very new). But the options were limited. JavaScript was often limited to AJAX requests, a modal or two, and some JQuery plugins. Very few people were "JavaScript Developers." They wrote JS for their webpages and Ruby/Python/Java/Whatever for everything else. But NodeJS and ES5 broke open the floodgates for JavaScript Development by elevating Javascript from something only seen in a <script> tag to a fullstack language. With that came a surge of new libraries, frameworks, methodologies, and opinions. It's exciting when a community grows so fast and puts out so much. Many old Javascript patterns and styless were declare obsolete and new ones were created. A new framework and stack seemed to come out every month. Suddenly Javascript needed build scripts and a pipeline. Grunt came along to solve that problem. Which was replaced by Gulp. Which was replaced by npm scripts. And now yarn? This rapid iteration of technologies appeared all across the Javascript ecosystem. Backbone, Angular, React, Vue, Angular 2. Flux, MobX, Redux. But these switches are as much a change in fashion than real improvements. But either way, the change takes effort to learn and implement. It turns out learning a new framework, library, pattern every 6 months is tiring. Its fun to learn something new. But having to constantly be learning, and at such a high rate, takes a lot of effort. That is the fatigue. The fatigue of every time you open up HN, there is some new JS library that will replace whatever you are using now. And if you don't switch, you are an idiot using old technology. Or at least the community makes you feel that way.
- duderific 10y ago
  That was a really great writeup of the issue, thanks for that.
dceddia 10y ago
The term "JavaScript Fatigue" came out of this post from about a year ago: https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4 https://medium.com/@ericclemmons/javascript-fatigue-48d4011b...

cwbrandsma 10y ago

Fatigue can be translated to "feeling worn out and overwhelmed". Basically, so much change you feel obligated to keep up with that you want to quit. I feel this a bit, there was a time when I could keep up with the changes going on in Javascript, but was overwhelmed by the changes happening in C# and Java (which for a time were going fast and furious). Now I'm ok with C# and Java...but Javascript is going berserk. It comes and goes.

Qwertystop 10y ago

New frameworks keep being made, becoming extremely popular, and then being dropped for the next new framework despite that they often do basically the same thing in roughly the same way. Some people are getting tired of this.

finchisko 10y ago

Thank you guys for explanation. I had feeling that it must be the thing you've described, but was not sure. I was missing js fatigue of what (context). To give example: js fatigue of new frameworks, js fatigue of constant changes... Anyway now I understand. PS: I don't feel js fatigue of any kind and actually like the pace js is progressing. I just don't jump on hype train anymore. Rather wait till things settle and prove their existence.

dexwiz 10y ago

The fatigue comes from having to constantly keep up with JavaScript and everything new. 5 years ago building JavaScript page was straight forward. Most of the time you would include JQuery from a CDN, and code in a server side template. If you were really serious, you used something like Backbone Or Ember (both very new). But the options were limited. JavaScript was often limited to AJAX requests, a modal or two, and some JQuery plugins. Very few people were "JavaScript Developers." They wrote JS for their webpages and Ruby/Python/Java/Whatever for everything else. But NodeJS and ES5 broke open the floodgates for JavaScript Development by elevating Javascript from something only seen in a <script> tag to a fullstack language. With that came a surge of new libraries, frameworks, methodologies, and opinions. It's exciting when a community grows so fast and puts out so much. Many old Javascript patterns and styless were declare obsolete and new ones were created. A new framework and stack seemed to come out every month. Suddenly Javascript needed build scripts and a pipeline. Grunt came along to solve that problem. Which was replaced by Gulp. Which was replaced by npm scripts. And now yarn? This rapid iteration of technologies appeared all across the Javascript ecosystem. Backbone, Angular, React, Vue, Angular 2. Flux, MobX, Redux. But these switches are as much a change in fashion than real improvements. But either way, the change takes effort to learn and implement. It turns out learning a new framework, library, pattern every 6 months is tiring. Its fun to learn something new. But having to constantly be learning, and at such a high rate, takes a lot of effort. That is the fatigue. The fatigue of every time you open up HN, there is some new JS library that will replace whatever you are using now. And if you don't switch, you are an idiot using old technology. Or at least the community makes you feel that way.

duderific 10y ago
That was a really great writeup of the issue, thanks for that.

dceddia 10y ago

The term "JavaScript Fatigue" came out of this post from about a year ago: https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4 https://medium.com/@ericclemmons/javascript-fatigue-48d4011b...