JavaScript状态2016：结果-CSDN博客

by Sacha Greif

由Sacha Greif

JavaScript状态2016：结果 (The State Of JavaScript 2016: Results)

等待已经结束 (The Wait Is Over)

I just looked through my inbox, and found a receipt for the awesome React for Beginners course dated November 4, 2015. So it’s been almost one full year since I ventured into the Wild West of modern JavaScript development.

我刚刚浏览了收件箱，发现了一张2015年11月4日出色的React for Beginners课程的收据。所以，自从我涉足现代JavaScript开发的狂野西部以来已经整整一年了。

I’m now fairly confident in my React skills, but it seems like as soon as I master one challenge, another one pops up: should I use Redux? Or maybe look into Vue instead? Or go full-functional and jump on the Elm bandwagon?

我现在对我的React技能非常有信心，但是似乎一旦掌握了一个挑战，就会弹出另一个挑战：我应该使用Redux吗？还是可以改用Vue ？还是全功能跳上Elm潮流？

I knew I couldn’t be the only one with these question, so I decided to launch the State of JavaScript survey to get a more general picture of the ecosystem. Turns out I hit a nerve: within a week, I had accumulated over 9000 responses (no meme intended)!

我知道我可能不是唯一一个提出这些问题的人，所以我决定启动JavaScript状态调查，以更全面地了解生态系统。原来，我很紧张：一周内，我已经积累了9000多个回复(无模因)！

It took me a while to go through the data, but the results are finally live!

我花了一些时间浏览数据，但结果终于生效了！

在这里查看调查结果 (Check out the survey results here)

And if you’d like to know a little bit more about the whole enterprise, just read on.

如果您想进一步了解整个企业，请继续阅读。

分析数据 (Analyzing the Data)

You might be wondering why it took me so long to analyze and publish the data. Hopefully this will become clear when you read through the report.

您可能想知道为什么我花了这么长时间来分析和发布数据。希望您在阅读报告时会清楚这一点。

I didn’t want to simply publish a bunch of charts with no context. Raw stats are great if you already know what you’re looking for, but if you’re looking for guidance then they can just as well add to the overall noise.

我不想简单地发布一堆没有上下文的图表。如果您已经知道要查找的内容，那么原始数据就很棒，但是如果您正在寻找指导，那么它们同样会增加总体噪音。

Instead, I decided to use these stats as a basis for a detailed report on the current state of JavaScript.

相反，我决定使用这些统计信息作为有关JavaScript当前状态的详细报告的基础。

作者 (The Authors)

I was originally planning on writing the whole thing myself, but I quickly realized that A) this would be a lot of work and B) I didn’t want the report to be too biased by my own preconceptions.

我原本打算自己编写整本书，但我很快意识到A)这将是很多工作，并且B)我不想让报告因我自己的先入之见而过分偏见。

So I asked a few developer friends to pitch in and write the various sections of the report. Not only is the overall report a lot more objective –and interesting– as a result, but I was also able to get experts for each topic (I’ll be the first to admit that there are entire swathes of the JavaScript world I know little about).

因此，我请几个开发人员朋友加入并撰写报告的各个部分。结果，总体报告不仅更加客观而且有趣，而且我还能够找到每个主题的专家(我将是第一个承认我几乎不了解JavaScript世界的所有人。关于)。

So a huge thank to all the authors who contributed to the report: Tom Coleman, Michael Rambeau, Michael Shilman, Arunoda Susiripala, Jennifer Wong, and Josh Owens.

非常感谢为报告做出贡献的所有作者：汤姆·科尔曼 ( Tom Coleman) ，迈克尔 ·兰博 ( Michael Rambeau) ，迈克尔·希尔曼 ( Michael Shilman) ，阿鲁诺达 ·苏西里帕拉 ( Arunoda Susiripala) ，詹妮弗·王 ( Jennifer Wong )和乔什·欧文斯 ( Josh Owens) 。

图表 (The Charts)

Here’s a little more info about the main types of chart you’ll see throughout the survey.

以下是有关您将在整个调查中看到的主要图表类型的更多信息。

堆积条形图 (Stacked Bar Chart)

This is the main chart for each section. For each technology, it shows the breakdown of developers who have never heard of it, have heard of it but aren’t interested/want to learn it, and have used it and would not/would use it again.

这是每个部分的主要图表。对于每种技术，它显示了从未听说过 ，听说过但不感兴趣 / 不想学习 ，使用过并且不会 / 不会再次使用的开发人员的细目分类。

You can toggle between percents and absolute numbers as well as filter by interest or satisfaction. But note that when filtering, the percentages are relative to the currently selected value pair (in other words both numbers total 100%).

您可以在百分比和绝对数字之间切换，也可以按兴趣或满意度过滤。但是请注意，进行过滤时，百分比是相对于当前选择的值对的(换句话说，两个数字总计为100％)。

热图 (Heatmap)

I also wanted to explore the correlations between each technology.

我还想探讨每种技术之间的相关性。

The heatmap charts achieve this by showing you how likely someone who uses one technology (defined as having selected “I have used X and would use it again”) is to use another technology, compared to the average.

通过显示热图图表，您可以看到与平均水平相比，使用一种技术(定义为选择“我已经使用X并且会再次使用X”)的某人使用另一种技术的可能性。

Pink means very likely, blue means very unlikely. In other words, a deep pink tile in the React row and Redux column means “React users are a lot more likely than average to also use Redux”.

粉色表示可能性很大，蓝色表示可能性很小。换句话说，React行和Redux列中的深粉红色图块表示“ React用户使用Redux的可能性也比平均水平高得多”。

建于 (Built With)

I decided to practice what I preached and build the survey app itself using modern JavaScript tools, namely React powered by the excellent Gatsby static site generator.

我决定实践我讲的内容，并使用现代JavaScript工具(即由出色的Gatsby静态网站生成器提供支持的React)自己构建测量应用程序。

It might seem weird at first to use React for what is essentially a static HTML page, but it turns out this brings a ton of advantages: for example, you’re able to use React’s vast ecosystem of modules such as the great Recharts library.

乍一看，将React用于本质上是静态HTML页面的页面似乎很奇怪，但是事实证明，这带来了很多好处：例如，您可以使用React的庞大模块生态系统，例如强大的Recharts库。

In fact I believe this may just prove to be a new, better approach for developing static sites, and I hope to write a more detailed post about it soon.

实际上，我相信这可能被证明是开发静态站点的一种新的， 更好的方法，并且我希望不久后写一篇更详细的文章。

伙伴 (Partners)

Finally, I wouldn’t have been able to take a month off to work on this without financial support from some really cool people.

最后，如果没有一些非常酷的人的财政支持，我将无法休假一个月来从事这项工作。

Both Wes Bos (who has put out the afore-mentioned React for Beginners as well as the new ES6 for Everybody) and egghead.io (which in my opinion is the single best resource out there for learning cutting-edge JavaScript development) accepted to sponsor the project. Thanks guys!

Wes Bos(推出了上述针对初学者的React以及面向所有人的新ES6 )和egghead.io (我认为这是学习尖端JavaScript开发的唯一最佳资源)都接受了赞助该项目。多谢你们！

支持项目 (Support the Project)

If you think what I’ve done here is valuable and would like to support the project, a tweet or share would be much appreciated!

如果您认为我在这里所做的事情很有价值并且想支持该项目，那么不胜感激或分享！

Additionally, you can also contribute a donation to get access to the raw anonymized data (or just enter “0” to get it for free).

此外，您还可以捐款以获取对原始匿名数据的访问权 (或只需输入“ 0”即可免费获得)。

下一步是什么 (What’s Next)

Now that the survey is over and we all know what the best technologies are, hopefully we can put any talks of “JavaScript fatigue” or “endless churn” to rest and move on with our programming lives.

既然调查已经结束，并且我们都知道最好的技术是什么，希望我们可以搁浅关于“ JavaScript疲劳”或“无休止的搅动”的讨论，并继续我们的编程生活。

Haha, as if!

哈哈，好像！

If one thing has become clear to me, it’s that the growing pains that JavaScript is going through right now are only the beginning. While React has barely emerged as the victor of the Front-End Wars of 2015, some developers are already decrying React for not being functional enough, and embracing Elm or ClojureScript instead.

如果对我来说清楚的是一件事，那就是JavaScript现在正在经历的不断增长的痛苦仅仅是开始。尽管React几乎没有成为2015年前端战争的胜利者，但一些开发人员已经在谴责React的功能不足，而是采用Elm或ClojureScript。

In other words, my job here isn’t done, and I fully intend to do this survey again next year! If you want to be notified when that happens, I encourage you to leave me your email here.

换句话说，我的工作还没有完成，我完全打算明年再次进行这项调查！如果您希望在发生这种情况时收到通知，建议您在此处留下我的电子邮件。

Until then, I can only hope these survey results will provide a little clarity in our never-ending quest to make sense of the JavaScript ecosystem!

在此之前，我只能希望这些调查结果能够为我们永无止境地寻求JavaScript生态系统的努力提供一点澄清！