Hacker News Reader

Comment by ng12 | Hacker News Reader

It's such a dumb argument that boils down to "things are changing and I don't like it!". Javascript fatigue is not real. I am completely convinced anyone who says otherwise has never had to maintain a non-trivial web application in Backbone/jQuery -- meaning they're complaining about frameworks that weren't built for their use cases.

View on HN

Javascript fatigue is real. Shit in front-end land changes so fast it is impossible to keep up with.

We just finished a rewrite from jQuery to Angular 1, with updates to all the tooling that goes along with it. We're now at least three years behind the curve... Hooray!

Meanwhile, the backend frameworks we've been using have had one minor version Nuget package release in the same timespan.

Angular 1 is 7 years old. And guess what? It's still a perfectly valid framework to build a web application with. There is no "curve".

Of course it's a valid framework. But the cool kids have all moved onto Angular2, or React, or some other thing I'm too stuck in the mud to even know about.

But why does that matter? Does your Angular 1 application work? Does Angular 2 existing prevent it from working?

Why did you rewrite the app from jQuery to Angular 1?

Any sufficiently large jQuery webapp has a strong tendency to become indistinguishable from a plate of spaghetti, without strong efforts to keep things sane. Angular, once we got over the learning curve and converted over the old functionality, made it a lot easier to make changes and add features.

No. It's "things are changing for no other reason than some overpaid FB brogrammers with too much time on their hands require Internet attention and need something to gloat over for the next conference."

Reply on news.ycombinator.com