[ThorinJacobs]

Tired of JavaScript? Not particularly. Tired of the #hype around JavaScript and more specifically the constant frameworks of the week? Absolutely.

I don't think this is a problem unique to JavaScript, however. We see the same sort of thing around technologies. Right now it's ML and Blockchain, earlier it was Cloud and IOT. The industry in general appears to be mostly built on inventing problems that can be solved by the tech, framework, etc. rather than leveraging technology to solve an existing problem.

This may be part of why you're having a hard time finding the problems JavaScript may solve for you. Personally, I find it much easier to follow the "Just In Time Learning" model https://blog.codinghorror.com/keeping-up-and-just-in-time-le.... Find out what parts you need in order to solve your problems, learn how they work, and leave the rest until you need it.

[williamxd3]

And I am tired of the "tired of JavaScript hype and new frameworks every week" speech.

It has a huge community, of course there will be new things created every week.

But, if it as bad you will not even hear about it, if you hear it is probably good or better on some aspects compared to others, who doesn't want that? do everyone wanted to be stuck with MooTools or JQuery forever?

[bluewalt]

The major problem is that when you learn something in this current crazy JS/Front world, your knowledge is deprecated 6 months later. I know a developer should always stay up to date with technology by constantly learning, but if I compare what I learned 5 years ago in Python, I would say 95% is still relevant today. But if I look at the JS "state-of-the-art" stack today, compared to the 2 years old, it's completely different. It's very frustrating to invest time and effort to learn something and then hear recruiters tell you things like: "Hmmm no one uses that anymore".

[williamxd3]

Maybe because there is no need to evolve there?

I mean, you can see clearly why we came from jQuery, to AngularJs, then Angular/React/Vue, there was a need.

[bluewalt]

This constant need to evolve is the exact definition of immaturity, for HTML/CSS/JS front-end.

I'm not a mobile dev, but I'm pretty sure when you make the front-end in an iOS app, you don't need to learn 3 languages + 2 frameworks + tooling to transpile + type checker + webpack...

Web front-end is completely broken because the foundation (HTML/JS/CSS) is not the right tool for the need.

[williamxd3]

Now that is a real problem, and it will not be fixed soon.

It is easy to a single company define how they want their platform to be, like iOS, but browsers are a different beast, as every change need to be agreed between several major companies.

[ThorinJacobs]

That's a totally reasonable sentiment and I can totally see how I didn't clearly articulate my feelings on the matter.

Of course we do want new tooling - ES6 and Angular in particular have worked well for me. Where I have some trouble is the tendency of some organizations to adopt these frameworks without considering whether the framework is actually solving a problem the have or expect to have in the near future. YAGNI is very tricky to get right.

[collyw]

JQuery works fine for most stuff. Not every app needs to be implemented as a SPA app, in fact I think many are better of with a more traditional architecture and a bit of jQuery. These days even jQuery doesn't seem especially necessary.