Live data from Hacker News

The State of JavaScript – Survey results

stateofjs.com

41–50 of 357 posts

Re: The State of JavaScript – Survey results

#41

ES6, CoffeeScript, and TypeScript all have near-perfect awareness, which surprised me since TypeScript isn’t quite as popular as the other two yet. I take issue with that statement. Just anecdotal, but I think these days Typescript is much more "popular" than CoffeeScript

Awareness just means "have heard of it". 99% have heard of Coffeescript but 14% want to use it in the future. 98% have heard of Typescript but 60% want to use it in the future.

Re: The State of JavaScript – Survey results

#42

Some interesting things on the "Front End Frameworks" page: * 53% of the respondents used React, and would do so again. * 47% use "No framework", and would do so again. (hmm. that doesn't leave much room, unless you can use more than one tool depending on the situation) * 43% had "no interest" in Angular 2. One other thing to consider, of the "had used X, would/would-not use again" responses: there is of course a lot…

The way I read it is that each question is independent.

So I can say I've used Angular and would never use it again while also saying I've used React and would use it again.

This is really a pretty decisively positive stat for React. Very few of its users would never use it again, while a lot of people have tried Angular and abandoned it. (This certainly matches my experience and anecdotes I've heard in the community.)

Re: The State of JavaScript – Survey results

#44
I appreciate that for the next year when there is a framework war I will have a link to shut it down.

Typically a newbie will ask about which framework they should learn. There will be a bunch of "it depends" and "try them out" responses, and then someone will take pity and pick a clear direction based on their experience.

Well and good.

But this way the newbie can learn from the actual experience of lots of other people. Data, for short.

Re: The State of JavaScript – Survey results

#45

Some interesting things on the "Front End Frameworks" page: * 53% of the respondents used React, and would do so again. * 47% use "No framework", and would do so again. (hmm. that doesn't leave much room, unless you can use more than one tool depending on the situation) * 43% had "no interest" in Angular 2. One other thing to consider, of the "had used X, would/would-not use again" responses: there is of course a lot…

For the record, you don't need to use Typescript for Angular 2, you can just use regular JS (or Dart for that matter). The documentation is definitely biased toward Typescript at the moment, but I anticipate the situation improving as the framework matures.

Re: The State of JavaScript – Survey results

#46

Never heard of the survey maybe the data is biased to only approach people on the silicon valley where technologies are used as if they were current season premium fashion cloths.

9k responses certainly weren't from SV alone. I know alot of the Spacedojo Slack channel took the survey and I think like 2 out of 300 live in SV.

Would be fun to maybe turn ip addresses into lat/long and map out where the responses came from...

Re: The State of JavaScript – Survey results

#47
post #35
post #18

Earlier quoted context omitted.

It's not so much that churn has been greatly reduced, but that the worst churn has started to be centralised and hidden behind tools like `create-react-app`. There will still be more churn as people come up with ways to be more productive, however it will be hopefully concentrated in areas other than build process tooling.

You're spinning this as a positive thing, but the fact that a UI library needs its own build tool does not speak well to the state of front-end development. Specifically the fact that we still don't have modules or widely-deployed http2 is what makes the build tool complexity necessary.

I wouldn't say that was spin, I said that build complexity is likely going to be handled by fewer engineers. The underlying problem still exists but less people need to put their oar in: that's bittersweet.

Re: The State of JavaScript – Survey results

#48

I apologize if the predictability of this comment, but I just want to say, I recently started a new gig at a company that has undergone a full on embrace of Javascript for tooling and server side projects and it boggles my mind how much productivity is wasted on this ecosystem. There is an interesting amount of energy put into making asynchronous code read synchronously in situations where asynchronous code provides…

> making asynchronous code read synchronously in situations where asynchronous code provides no benefit

It's analogous to how everybody jumped to document-based databases a few years ago and gradually developed an RDBMS-like schema system enforced only by coding conventions.

Re: The State of JavaScript – Survey results

#49

Never heard of the survey maybe the data is biased to only approach people on the silicon valley where technologies are used as if they were current season premium fashion cloths.

9k responses certainly weren't from SV alone. I know alot of the Spacedojo Slack channel took the survey and I think like 2 out of 300 live in SV. Would be fun to maybe turn ip addresses into lat/long and map out where the responses came from...

exactly this is my point, maybe the data is biased to US developers mostly

Re: The State of JavaScript – Survey results

#50

I appreciate that for the next year when there is a framework war I will have a link to shut it down. Typically a newbie will ask about which framework they should learn. There will be a bunch of "it depends" and "try them out" responses, and then someone will take pity and pick a clear direction based on their experience. Well and good. But this way the newbie can learn from the actual experience of lots of other pe…

The same, from my slightly different perspective: I've been away from JavaScript for 3 years, and it is awesome to have a resource to help navigate the way back in, and get the most bang-for-my-buck, so to speak.

I can tell here what tech I need to focus on for my pet project, which will also improve my hirability looking forward.

Post reply on HN