Super interesting. Lots of data there. Two things that stood out from a quick once-over: Vue is doing better than I expected. PostCSS is less adopted than I expected.
I just tried Vue 2.0 for the first time last week and I really really liked it.
The State of JavaScript – Survey results
11–20 of 357 posts
Re: The State of JavaScript – Survey results
#12I really liked the "features" section. I've seen some weird things done in the wild to obtain some of these features. Like building a multi-SPA to obtain code-splitting where a site is split up into multiple pages each acting as their own SPA. But it does seem like things are settling down. Envious of all the people starting now. As someone who started web dev in 2010, anything I learned that was framework-specific then, is almost completely obsolete now lol.
Re: The State of JavaScript – Survey results
#13This seems to suggest the rate of framework churn has rather settled down. Are JS devs finally starting to be satisfied with their current tools and not needing to restart every 18 months?
I see this same, tired old meme in every thread about web technologies. It's funny to me that certain people are so disdainful of the churn in web development on a forum dedicated to "hackers". Web application development is hard, and the reason why there's so much churn is because smart, inventive people are constantly finding better ways to do things. Things aren't just resetting from scratch every 18 months. The w…
I agree that a lot of the churn is each generation (a generation here seeming to be about a year) of tools learning from and building upon the former. Obviously the churn is continuing since developers realize that the tools are quite "there" yet. My hope is that some year we will finally reach "there" (not perfection, but highly good enough) and the churn will slow down to the point that perhaps the generation time period will stretch out to five years or so.
Re: The State of JavaScript – Survey results
#14Some 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 of selection bias of whether or not to even try X in the first place.
...
My only experience with these so far is Angular 1. It's easy to get started with, but does get messy when you have a very large form (think "government work"). I don't have a "React" axe to grind, I'm just looking at the numbers.
However, by the time I have to haul in Typescript transpiling, much of the appeal of Angular 1 is lost :-(
(it feels like GWT, all over again, at least to some extent)
Re: The State of JavaScript – Survey results
#15Nice design.
Re: The State of JavaScript – Survey results
#16ES6, 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
Re: The State of JavaScript – Survey results
#17This seems to suggest the rate of framework churn has rather settled down. Are JS devs finally starting to be satisfied with their current tools and not needing to restart every 18 months?
Some forms of "churn" are also called "progress". Is the current crop somehow better than the previous?
Re: The State of JavaScript – Survey results
#18This seems to suggest the rate of framework churn has rather settled down. Are JS devs finally starting to be satisfied with their current tools and not needing to restart every 18 months?
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.
Re: The State of JavaScript – Survey results
#19According to the survey, 213 people that took it have never head of plain javascript.
To be fair, a side effect of JS Fatigue is the inability to tell whether "Plain JavaScript" is the newest kid on the block or if it really means "good old JavaScript (ES3)".
Especially when the headline is "JavaScript Flavors".
Re: The State of JavaScript – Survey results
#20ES6, 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
It's got the Microsoft Seal of Approval(TM)!
Yeah, doesn't mean much to me, but it does guarantee you can get tools that are compatible with it.