Live data from Hacker News

The State of JavaScript 2018

2018.stateofjs.com

91–100 of 286 posts

Re: The State of JavaScript 2018

#91
post #56
post #29

Earlier quoted context omitted.

But we don't know if people mean AngularJS (1) or Angular (2+) here. In my opinion, while angularJS is now getting a bit outdated and very different under the hood, for a user it's pretty similar to Vue.JS, which people do seem to love. Angular 2+ on the other hand seems to have added a layer of JavaEE-like over-engineering on top. I think a framework should be written with productivity as top concern and Angular 2+…

They're similar? Then I know to avoid Vue and stick to React.

I have plans to look more deeply into Vue when I have some time since so many people like it, but that's the impression I get from it, it does a heap of the stuff I didn't like about angular, why would I go back?

Re: The State of JavaScript 2018

#92
post #66
post #42

Earlier quoted context omitted.

> Angular is dead? Most don't even want to touch it again ( Great ). Yet what I see around me is enterprise customers on our projects adopting Angular as the official internal Framework, as React is seem as too advanced.

Most of HackerNews isn't enterprise hackers. At least the active commentators.

Is that the assumption or for fact? I see people with very diverse background here.

Re: The State of JavaScript 2018

#93
post #87

I believe JS will be the universal language in the next 5 to 10 years. Other languages will continue to exist but 90% of developers will do JS... I can't wait to quote myself in the future :p

With the advent of WASM I'd be inclined to think otherwise: better languages eating javascript's lunch.

One can hope.

Re: The State of JavaScript 2018

#94
post #5

Ouch, the ratio of "would use again" to "would not use again" on AngularJS stunning, if not surprising: https://2018.stateofjs.com/front-end-frameworks/overview/

Wasn't there some kind of huge upgrade pain between versions (v1 to v2 I think it was) for people? I vaguely remember talking with some folks at work who were trying to upgrade at one point, and they ended up changing frameworks entirely (to react) because the effort to upgrade was considered "about the same as a rewrite".

That is certainly the case. Google's decision for Angular have made millions of lines of code legacy over night.

The real reason it ever got traction in my opinion was the built in dependency injection. It solved a real problem at the time, but ES6 modules make it a lot less appealing now.

Re: The State of JavaScript 2018

#95
post #43

One important data point there is Visual Studio Code. It used to be really popular in 2017 (double the popularity of Atom/Sublime/Webstorm), now it's just eating everyone's lunch (triple the popularity of Sublime/Vim/Webstorm/Atom, almost equal to all of them combined). Also Atom is declining sharply. Compare https://2018.stateofjs.com/other-tools/ to https://2017.stateofjs.com/2017/other-tools/

Fully deserved from where I stand.

I have 3 editors I regularly use, emacs when I need to edit something in a terminal (eg ssh'ed somewhere), Intellij when I need a full blown IDE (refactoring and debugging), VSCode for everything else.

It's fast, well updated, works well ...

Re: The State of JavaScript 2018

#96
post #18

People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…

Loved? Well, it's a point of view. I personally hate it, due to the tooling and the dependency management (npm and yarn are catastrophic, an "hello world" example with React downloads on average more than 100 packages).

My "secret" weapon against tooling creep is https://parceljs.org it really lives up it its tagline.

Re: The State of JavaScript 2018

#97
post #42
post #18

People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…

> Angular is dead? Most don't even want to touch it again ( Great ). Yet what I see around me is enterprise customers on our projects adopting Angular as the official internal Framework, as React is seem as too advanced.

The survey results this year is misguided as it now mixes AngularJS with Angular. Was surprised they made such remarks in the conclusion knowing this change. Most AngularJS users will not use it again for sure.

Re: The State of JavaScript 2018

#99
post #42
post #18

People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…

> Angular is dead? Most don't even want to touch it again ( Great ). Yet what I see around me is enterprise customers on our projects adopting Angular as the official internal Framework, as React is seem as too advanced.

Since I mostly work in the enterprise (in Europe) I see Angular all around me as the de facto framework. It's definitely not dead. With TypeScript it's a pleasure to work with.

I think a lot is due to the unfortunate naming, people still confuse AngularJS (v1) with Angular (v2-v7). I totally believe a lot of folks will say "Used AngularJS (v1) won't use it again".

Post reply on HN