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

111–120 of 286 posts

Re: The State of JavaScript 2018

#111

Post by vanderZwan »

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

Re: The State of JavaScript 2018

#112

Post by sAbakumoff »

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…

IMHO Angular in its recent versions is the most simple front-end framework ever. It's not even JS anymore. It's type script + reactive framework. Those 2 things makes programming extremely easy.

Re: The State of JavaScript 2018

#113

Post by nkjoep »

rpwverheij wrote: post #75
pjmlp wrote: 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.

as someone who tried Angular and was so relieved with the simplicity of React, I have no idea how they can come to that conclusion. But then again, I'm not very well know with the field of enterprise customers

I've got the same feeling but with bad connotation.

React is easy the same way jQuery is. Easy, unstructured, foggy, too much permissive tool.

Far too easy to end-up with spaghetti-code.

I prefer not using it, Angular is far more organized.

Re: The State of JavaScript 2018

#114

Post by esistgut »

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 using NativeScript and a somewhat Angular-esque backend development framework using Nest.js. Seems like a good deal to me.

Re: The State of JavaScript 2018

#115

Post by suprfnk »

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?

> Note that from this year on, we will not be making a distinction between Angular and Angular.js.

At the top of: https://2018.stateofjs.com/front-end-frameworks/angular/

Re: The State of JavaScript 2018

#116

Post by Bahamut »

I can’t remember prior years, but browsing this site on mobile has been the most painful web browsing experience for me in years (iOS Safari).

Consider the design of the site in the future and mobile browser behavior - for example, tapping the bottom right button to navigate to the next view brings up the toolbar on Safari instead of navigating to the next page.

Re: The State of JavaScript 2018

#117

Post by chrisweekly »

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…

One major reason is that Ng is its own thing. It's not JavaScript, nor HTML. Also, "batteries included" means buying into the whole monolithic framework. The React ecosystem requires more decisions, but also benefits from ability to pick and choose the right libraries for a given project. That said, Angular has some great parts, eg TypeScript and RxJS.

Re: The State of JavaScript 2018

#118

Post by thrower123 »

devxpy wrote: post #64
arnvald wrote: post #59

Earlier quoted context omitted.

I suspect one of the reasons people are happy with JS (even though there's plenty of much better languages) is that it has made a huge progress. Writing ES6 after a few years with ES5 is so much more pleasant. I used to be annoyed every time I had to write some JS code in the past, now I must say I even enjoy it. However, regarding the metric that shows developers' happiness over the years: * If someone asks me if I'…

I think we should also consider that most people have gotten used to the fact that JS is the language of the web, and there’s basically nothing we can really do about it in the short term, so let’s just have a positive attitude towards it! P.S. I don’t, but most people I have met seem to have this kind of mentality.

Yep, the Stockholm Syndrome. I still swear a blue streak when I get pulled from my nice backend world over to do some trivial UI work on the front-end, and it takes me frigging forever because there's no type system, and no compiler, and the tooling is stone age, and it takes me longer to run gulp and babel to build it to see changes than building my entire backend solution and running all my tests.

It's all we've got, but it is assuredly not good. Hopefully WebAssembly comes to fruition and we can leave this dark era behind.

Re: The State of JavaScript 2018

#119

Post by gagege »

bryanrasmussen wrote: post #30
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…

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.

Re: The State of JavaScript 2018

#120

Post by bryanrasmussen »

gagege wrote: post #119
bryanrasmussen wrote: post #30

Earlier quoted context omitted.

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…

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.

yes that would be nice, but then lots of things that do not match reality would be nice.
Post reply on HN