The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.
I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.
Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.
npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.
I don't think I need to make clear that this is a weird trend. How to explain it?
Maybe: lots of people in 2017 wanted to try Angular, tried it, and almost none of them liked it.
Or maybe: new users are still liking it but old users are churning out?
Over in data layers, Apollo comes in at 11% - it was at 6% in January, and this is exactly the growth I would expect. GraphQL overall is in at 20% with very few abandoners so far. It remains the tech I expect people to dig into in 2019.
The only other note here is that Redux at 47% is a lot higher than npm's data would suggest, but we didn't ask about Redux directly, so this more of a note to myself about improving our survey and translating our downloads data into real usage.
63% of respondents say they would like to learn GraphQL. Damn!
Back-end frameworks. Several interesting tidbits here:
- Next.js has an enormous "want to learn" pool, great sign for them
- 62% of Meteor users and 72% of Sails users would not use them again, ouch

We need to stop calling Express a framework, it's too big. It's bedrock.
In Native App land, Electron is lower here (20%) than npm's data (24%) but still, 24% of people is just enormous adoption, amazing work there. React Native is almost as big at 19%. Some really tough abandonment numbers there for Ionic and especially Cordova.
This is some really great data, well-presented. Congratulations to @sachagreif, @benitteraphael and @michaelrambeau on their hard work here. It's really nice to see this survey and npm's largely in agreement, since it can give us all more confidence in the accuracy of our data.
P.S. I am still puzzling about the Angular data. Apparently in 2018 more people (34%) decided to stop using Angular than were using it at all in 2017 (29%). It's not impossible that lots of people tried it but didn't like it in 2018 but it's a really surprising outcome.

More from Tech

I think about this a lot, both in IT and civil infrastructure. It looks so trivial to “fix” from the outside. In fact, it is incredibly draining to do the entirely crushing work of real policy changes internally. It’s harder than drafting a blank page of how the world should be.


I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.

Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.

And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.

God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.

For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.

That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.

You May Also Like

TradingView isn't just charts

It's much more powerful than you think

9 things TradingView can do, you'll wish you knew yesterday: 🧵

Collaborated with @niki_poojary

1/ Free Multi Timeframe Analysis

Step 1. Download Vivaldi Browser

Step 2. Login to trading view

Step 3. Open bank nifty chart in 4 separate windows

Step 4. Click on the first tab and shift + click by mouse on the last tab.

Step 5. Select "Tile all 4 tabs"


What happens is you get 4 charts joint on one screen.

Refer to the attached picture.

The best part about this is this is absolutely free to do.

Also, do note:

I do not have the paid version of trading view.


2/ Free Multiple Watchlists

Go through this informative thread where @sarosijghosh teaches you how to create multiple free watchlists in the free


3/ Free Segregation into different headers/sectors

You can create multiple sections sector-wise for free.

1. Long tap on any index/stock and click on "Add section above."
2. Secgregate the stocks/indices based on where they belong.

Kinda like how I did in the picture below.