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

131–140 of 286 posts

Re: The State of JavaScript 2018

#131

Post by atom-morgan »

esistgut wrote: post #114
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…

> Angular is dead? Most don't even want to touch it again ( Great ). I don't get the Angular hate. I work with it daily and seems like a productive environment. I did some tests with React and Vue too and couldn't find any relevant advantage. Angular has batteries included tools for a lot of tasks: i18n, routing, isomorphic builds, web components, etc.. You get a cross platform mobile development environment too usin…

I think they could have avoided 90% of their problems by just giving it a different name.

Re: The State of JavaScript 2018

#132

Post by arxpoetica »

userbinator wrote: post #121
gagege wrote: post #119

Earlier quoted context omitted.

I think he kind of had a good point. It would be nice to have a single set of tools that can always get the job done no matter what.

Not long ago I had to write some JS (had to, not wanted to) to do something on a site, and got something working based on what I knew, only to be derided by a "real JS developer" that my code was "deprecated", "not following best practices", "not modern", etc. He gave me his version which was around 10x more code and only worked in a subset of the latest browsers, while mine not only did but would probably work in ev…

Sounds like he wasn’t a very good JS dev...?

Re: The State of JavaScript 2018

#133

Post by bryanrasmussen »

userbinator wrote: post #121
gagege wrote: post #119

Earlier quoted context omitted.

I think he kind of had a good point. It would be nice to have a single set of tools that can always get the job done no matter what.

Not long ago I had to write some JS (had to, not wanted to) to do something on a site, and got something working based on what I knew, only to be derided by a "real JS developer" that my code was "deprecated", "not following best practices", "not modern", etc. He gave me his version which was around 10x more code and only worked in a subset of the latest browsers, while mine not only did but would probably work in ev…

if someone ended up with 10X the code using 'modern' JS and it did not work cross-browser while yours worked cross-browser including IE6 and up, then I strongly suspect I would prefer yours.

Re: The State of JavaScript 2018

#134

Post by meigwilym »

sgdesign wrote: post #14
Digit-Al wrote: post #6

Earlier quoted context omitted.

Not a question but a suggestion. I live in England and am very aware that the residents of Scotland and Wales don't like to be classed as "English". You might want to change the title to the more neutral (and correct) Britain, Great Britain, GB, United Kingdom, or UK.

Oh I didn't even see that, thanks for the feedback!

Here's a map to explain the difference.

https://www.ordnancesurvey.co.uk/blog/2011/08/whats-the-diff...

Re: The State of JavaScript 2018

#135

Post by sgdesign »

daxterspeed wrote: post #125
nailer wrote: post #100

As a survey completer, they still don't include ES8 as an option: https://2018.stateofjs.com/javascript-flavors/overview/ 'await' is a game changer for JavaScript: major libraries like Stripe and Hapi are rebuilding their docs too be ES8 based.

I believe the survey uses ES6 (which officially is named ES2015) to refer to the "current version" of ECMAScript (which I suppose is ES2017). I don't know if the solution is to include each yearly release of ECMAScript since ES6, or to simply add an "ES.Current" option, which would just be the latest proper release.

Next time I think we'll just drop the ES* item altogether and instead ask developers which JS language features they use directly.

Re: The State of JavaScript 2018

#136

Post by nailer »

daxterspeed wrote: post #125
nailer wrote: post #100

As a survey completer, they still don't include ES8 as an option: https://2018.stateofjs.com/javascript-flavors/overview/ 'await' is a game changer for JavaScript: major libraries like Stripe and Hapi are rebuilding their docs too be ES8 based.

I believe the survey uses ES6 (which officially is named ES2015) to refer to the "current version" of ECMAScript (which I suppose is ES2017). I don't know if the solution is to include each yearly release of ECMAScript since ES6, or to simply add an "ES.Current" option, which would just be the latest proper release.

Well yes, that's my point. There's a massive difference between using class and template strings with callbacks or 'then' vs actually using Direct Style with 'await'

Re: The State of JavaScript 2018

#137

Post by fybe »

bobince wrote: post #63

The State of JavaScript 2018 is inaccessible in IE. That seems about right.

It's hilarious. Doesn't work in IE, in Edge the button to start doesn't show and if you go directly to https://2018.stateofjs.com/introduction/ the navigation and styling is broken.

And in 10 the floating squares don't even show up. And it doesn't have fall-back for browsers with no SVG support - really nitpicky but it is an actual problem.

Re: The State of JavaScript 2018

#138

Post by no_gravity »

vanderZwan wrote: post #111
no_gravity wrote: post #70

It is interesting to compare the popular front end frameworks year over year. The percentages for 'Used it, would use it again': 2017: React: 58% Vue : 20% 2018: React: 65% Vue : 29% So both have been growing at a similar pace. Not sure about Angular, as in 2017 they listed 'Angular 1' and 'Angular 2'. This year only 'Angular'. Is that the combined number for both versions?

> So both have been growing at a similar pace. Don't know if you can compare these numbers that easily: one increased their userbase by 12%, the other by 45%.

I think that measuring relative numbers would make sense if we assume exponential growth. But looking at 2016,2017 and 2018, it seems to be rather linear:

https://2018.stateofjs.com/front-end-frameworks/vuejs

Re: The State of JavaScript 2018

#139

Post by oblio »

tomas789 wrote: post #92
oblio wrote: post #66

Earlier quoted context omitted.

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.

I don't have stats to back it up, talk to pg for that :)

But it's not that hard to figure out based on comments, upvotes, stories on the front page, etc.

Consider it an educated guess from a relatively active HN member who's been here for 5 years :)

Re: The State of JavaScript 2018

#140

Post by yesimahuman »

pjmlp wrote: post #42
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…

> 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.

Same. I don’t think this survey is representative of the enterprise at all. In fact, it seems like responses are down this year from last year from what I can tell. 20,000 is not a huge sample size in this market.
Post reply on HN