Found this on YouTube..

With all the major library/framework overhauls in the JS community, I feel we may need to start versioning in our resumes:

angular@2.4
react-router@4.0.0-alpha.5
jest@19.0.2
..

New JS framework

(IT AIN'T EVEN 4 WORDS)

Fuck javascript. I am moving on. Here I come OCaml and Reason.

What should I go for? AngularJS, ReactJS, EmberJS or VueJS? I'm confused. Help!?

Why node hurt so much.
#javascriptfatigue

I don't consider myself a guru in JavaScript (hell I studied theoretical chemistry), but I do hate much of the rationalization behind building a Jenga stack of libraries, frameworks, dependencies... for building everything web related.

Many of the problems I see people solving with these giant stacks could be easily solved understanding how websites work (html, css, js and how interact with each other) with no dependencies giving smaller (for end users at least) and more maintainable code (in the sense it would not require updating dependencies that may be discontinued...)

I do imagine situations where these are ideal... Since there are not absolutes and developing is very context sensitive, but man if I have js article fatigue for ridiculous scenarios.

Has anyone ever installed a NPM package without seeing deprecation warnings? 🤦‍♂️

I just learned vue.Js, its very easy to learn, and it introduced me to node js, now i can build node apps with express and i can even use modules and build my proper ones.
#javascript #VueJS

I think it's easier said than done guys. And 'better' is sometimes over-rated. What do you think?

Four new JavaScript frameworks have been released this year!

const getAgenda = weekday => weekday === 'saturday' ? 'work' : 'work'

So, is someone still using NPM?
That's so last year!

People are whining about frontend bloat, overengineering, too many packages on npm and whatnot.

And I'm just like: "Hey! You still can write your own leftpads y'know..."

I just don't get​ why having lots of options has to be so bad...

That no one can agree to write code the same way, use the same framework, or use the same tooling. Thank you js fatigue.

How the faculté of choice can be at the same time a wonderful delight as well as a freaking pain in the ass. espcially when considering JS frontend