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

101–110 of 286 posts

Re: The State of JavaScript 2018

#101

Post by krona »

daliusd wrote: post #61
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…

> TypeScript is gaining ground, people are moving away from Flow. Is it really the case? Both projects are watched and have quite big number of stars in github. I have tried flow and liked it. I have used typescript in the past and I'm not crazy about it. Therefore I would like to get better understanding here. Is there anything I could read about it?

The proportion of Flow users who said "would not use it" has increased substantially over the past year. (24% vs 41%)

Re: The State of JavaScript 2018

#102

Post by krona »

jaxondu wrote: post #86
daliusd wrote: post #61

Earlier quoted context omitted.

> TypeScript is gaining ground, people are moving away from Flow. Is it really the case? Both projects are watched and have quite big number of stars in github. I have tried flow and liked it. I have used typescript in the past and I'm not crazy about it. Therefore I would like to get better understanding here. Is there anything I could read about it?

Don’t have to take the survey so seriously. It’s not representative of all JS community. My circle of JS hackers don’t even bother to participate.

Is there any reason to suspect Flow users are less likely to do the survey than, say, TypeScript users?

Re: The State of JavaScript 2018

#103

Post by pjmlp »

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

React requires too much FP concepts for the typical average enterprise developer.

It feels like doing Haskell with JavaScript.

Re: The State of JavaScript 2018

#104

Post by enturn »

sgdesign wrote: post #2

Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")

The links to learn more in the popovers on the other libraries page [1] are impossible to click since they disappear when not hovering over the name. Apologies if someone has mentioned this before. Edit: I'm using Waterfox. It works well in Chrome.

1. https://2018.stateofjs.com/front-end-frameworks/other-librar...

Re: The State of JavaScript 2018

#105

Post by pjmlp »

intothemild wrote: post #80
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?

I would have broken Angular into two categories.. 'Angular 1' and 'Angular 2+' From what I've seen, if there's an Angular project it's still Angular 1

Only Angular 5 around here.

Re: The State of JavaScript 2018

#106

Post by fsloth »

de_watcher wrote: post #73
gear54rus wrote: post #22

Earlier quoted context omitted.

...yes it is?

Using JS through time is like observing a freshman student who discovers new stuff in old books. Amusing, but we've got better things to do.

That's a fantastic analogy!

I suppose the analogy in medicine would be to have this "medical hacker" mentality where you just go and do things, all the while learning. First you start with leeches, then you develop your own theory or four humours, https://en.wikipedia.org/wiki/Humorism, then you figure out there was this guy called Hippocrates who had lots of great ideas about medicine which you should totally read, but hey, who has the time nowadays, so you just skim through a blogpost with the summary of the most interesting tidbits.

You keep hearing the name "Pasteur" and the "germ theory of disease" which sounds mildly intimidating. Instead, make your own plague doctor mask with a organic herbs as a safekeep. That'll keep the germs away.

People think your plague doctor mask is really cool in instagram and you become moderately famous. People start asking medical advice from you. They keep mentioning something called "vaccines", which sounds really convenient. You read an obscure reference about primitive vaccination to smallpox and decide that's a great idea. You start scratching yourself with random things you find in the street to increase your "resistance" to all ills.

You create a blog around this cool concept of "resistance" and invite other people to scratch themselves. Someone dies from infection and you say they just can't use the tool right....

etc.

I presume the protagonist will eventually reach modern medicine if he's alive still, but it would be so much more convenient for all parties if he had become familiar with established standards before starting to share his ideas with the greater public.

Re: The State of JavaScript 2018

#107

Post by steveklabnik »

alkonaut wrote: post #72
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…

The State of Rust is a yearly survey: Unsure if the 2018 results are done? https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Resul...

Still analysizing them. Soon though!

Re: The State of JavaScript 2018

#108

Post by georgecalm »

No surprises here this year: es6 & typescript, react & vue. I think I’d put redux and graphql in different categories as they’re not mutually exclusive. Nevertheless, I’m happy to see excitement for the latter.

Re: The State of JavaScript 2018

#109

Post by benjaminsuch »

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…

Just curious why no one want to touch it again? I never developed with Angular but I loved to develop with AngularJS (and still working with it). Can anybody entlighten me?

Re: The State of JavaScript 2018

#110

Post by AllegedAlec »

gear54rus wrote: post #82
de_watcher wrote: post #73

Earlier quoted context omitted.

Using JS through time is like observing a freshman student who discovers new stuff in old books. Amusing, but we've got better things to do.

well it's certainly better than listening to ranting retrograde gramps "zomg new framework, I have to LEARN again :("

This is a fairly vacuous remark, if I'm frank.

The problem isn't that you have to learn another framework (although it does become a problem when they're all slightly similar and they start to meld together after the umphteenth, not to mention that learning slows down with age). The problem is that each frameworks brings along new edge cases, new problems and forces you to reinvent tools you already had for this new framework. Although learning new shit can be exiting, at some point, you gotta stick to something for a while so you can also actually build a lasting product with it, rather than building a new prototype but never finishing anything because you're distracted by a new shiny.

Post reply on HN