JavaScript Burnout & Fatigue - From Vanilla JS, Libraries & Frameworks

JavaScript Burnout and Fatigue are real and in this video, I share with you my thoughts on what causes JavaScript Developers to burnout and sometimes quit.

*Fix NPM Vulnerabilities*

Learning to code with JavaScript isn't actually that hard. But the amount of knowledge you'll need to learn to become a Full Stack JavaScript Developer can be extremely intimidating.

JavaScript is one of the most versatile coding languages that can be used anywhere from web design and development, to desktop applications, iOS or Android development, it seems JavaScript has no limit to its use case.

First learn the fundamentals of JavaScript. Then learn a framework or library, maybe learn a package manager or task runner. The list of tools developers use when programming in JavaScript seems endless.

Here's a shortlist of libraries and frameworks and tools you might use with JavaScript.

You most likely heard of jQuery, what about React or React Native. Have you heard of Vue JS or Angular? What about NodeJS? Maybe you use Grunt or Gulp, or maybe you use Webpack.

If you want to use next generation JavaScript, then you most likely use Babel.

The list goes on and on. Watch this video on JavaScript Burnout and Fatigue to get more insight into the Land of JavaScript and it's impact on programmers.

#javascript #js #programming

[bobbysilver]

This reminds me of guys doing road repairs. Lot's of discussions take place around the machines, equipment and road layout. Everyone talking about the latest spade, truck or digger. Then there is one or two guys actually in the hole getting the work done.

[kadoacademy]

Great Content, i like this as it's really helpful
This problem mostly face Junior developers, when they start seeing nightmare on Javascript they start Jumping to Js frameworks instead of having the solid understanding of Javascript itself first, this what makes them lose hope on Js.
I like the way you explained it more practically. Big up to you dude👊

[be-kreidly]

Thank you for the nice video! What Javascript online platform you suggess for vanilla JS challenges?

[lucasluckylucas]

Help, when i download, it says. the archive is either in unknown format or damaged. what to do?

[chrisanderson]

I chose Svelte with TypeScript for the frontend. For the backend... eh, I'm still not sure. TypeScript on NodeJS, with probably Express v5 (async support).

[FnordSho]

or, one could use some serious languages on front-end, like Elm or Dart and be free from chaotic JS ecosystem. people are creating more and more frameworks because language is poorly designed. once the language matures, people move on to working, maybe sometimes coding some libraries, and nobody is trying to reinvent the entire ecosystem and enjoys being a happy dev :)

[RamonChiNangWong]

I agree, I hated jQuery back then when it first came out and I hated now and it's clones

[dera_ng]

So your solution is to set yourself up to manage or reduce the time spent suffering?

Damn! What a revolutionary strategy!