Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The State of JavaScript 2018

2018.stateofjs.com

Post reply on HN
Print view View original

21–30 of 286 posts

Re: The State of JavaScript 2018

#21

Post by stock_toaster »

s_kilk wrote: 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".

Re: The State of JavaScript 2018

#27

Post by IloveHN84 »

ksec wrote: 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).

Re: The State of JavaScript 2018

#28

Post by sgdesign »

tommyjepsen wrote: post #24

Is "Angular's Popularity Over Time"'s bad stats based on combining Angularjs and Angular2 into one?

In previous surveys we had both Angularjs and Angular, but starting this year we stopped making the distinction. So yes, the "bad" stats include both versions. It's not perfect but we thought it was best to just bite the bullet and combine both going forward.

Re: The State of JavaScript 2018

#29

Post by kabes »

s_kilk wrote: 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/

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+ is anything but that, it constantly works against you.

Re: The State of JavaScript 2018

#30

Post by bryanrasmussen »

LandR wrote: post #12

> JavaScript is always changing. New libraries, new frameworks, new languages… It's part of the fun, No.. NO, it isn't.

I'm reminded of back in 1997 (maybe 98, anyway long time ago), I had been on a JavaScript course with a British guy, and went over to his house. He showed me the little cv site he'd been working on, it had quite a nice design, much better than I would ever do if asked to design something. I looked at the code - it was all tables, so I decided to show him CSS at the end of which he thunderously proclaimed "That's what's wrong with this industry, there's always something new to learn!"

I think he's doing something with Sitecore now, make of that what you will.

Post reply on HN