Hacker News Reader

Comment by fenomas | Hacker News Reader

And thus, yet another insipid "hey let's argue about JS fatigue!" comment clobbers another HN comment page, with 100+ replies not one of which has anything to do with TFA.

View on HN

If it wasn't a problem, it wouldn't be upvoted. That is how voting works. I'm not a JavaScript programmer, although I have dabbled extensively in the past. My impression of this thread is that not much has changed in that world. Sencha, titanium, and Phonegap were super hot back in the day, along with jQuery, SproutCore, Knockout and Backbone. Now it is all different for JS. That fuckng sucks.

> If it wasn't a problem, it wouldn't be upvoted.

It's upvoted because it's HN's current favorite holy war. "Front-end development is out of control" is something everyone has an opinion about, in a way that the announcement of React Fiber isn't.

That doesn't mean the same debate needs to be re-litigated every two days. Occasionally would be fine, but when it happens in every tangentially related thread it sucks the oxygen out of everything else.

Because it is out of control! You have to have some serious "nalgas" to dive in... I tried some years back and said; "F this" I am going to learn Python and Java. I am not even paid to program in most cases. There is a LOT to be said about stability.

It does need to be reignited or it wouldn't be. It is like being a climate change denier at a climate conference. "Uhhggg why are we talking about this again?" I don't believe its a problem... Well, shit loads of people do!!!!!! SO suck it up buttercup.

"Look, I know it's an off-topic rant, but this issue is so important than it warrants off-topic rants!", said everyone who's ever posted an off-topic rant.

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.

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