by Sacha Greif

由Sacha Greif

誰參加了JavaScript 2018狀況調查？ (Who Took the State of JavaScript 2018 Survey?)

我們如何努力使調查更具代表性 (How we’re working to make the survey more representative)

I was recently listening to a podcast episode about the State of JS survey and while the hosts were appreciative of our efforts, they also had a few criticisms about our methodology.

我最近正在聽有關JS狀況調查的播客，當主持人贊賞我們的努力時，他們也對我們的方法提出了一些批評。

Mainly, that it wasn’t clear who exactly took the survey, how they found the survey, and whether that population sample was representative of the overall JavaScript ecosystem.

主要是，不清楚是誰確切地進行了調查，他們如何找到調查以及該人口樣本是否代表了整個JavaScript生態系統。

Those are valid questions, so let’s address them.

這些是有效的問題，所以讓我們解決它們。

代表……什么？ (Representative… of What?)

First, let’s address the question of “representativeness”. When you run a political poll to figure out how people are going to vote, you have a clear referential: the country’s total voting population.

首先，讓我們解決“代表性”問題。當您進行政治民意調查以了解人們如何投票時，您會得到一個明確的參考：該國的總投票人口。

A government census tells you how many voters there are and what their demographic breakdown is, which lets you compare your own poll to this data to figure out how representative your results really are.

政府人口普查告訴您有多少選民，以及他們的人口統計細分，這使您可以將自己的民意調查與該數據進行比較，以確定結果的真實性。

When it comes to the “JavaScript ecosystem” though, we don’t have a clear referential.

當涉及到“JavaScript的生態系統”，雖然，我們沒有一個明確的參考。

From a senior engineer working on a 100+ developer team for a Fortune 500 company to a high-school student hacking on a JavaScript transpiler in their spare time, anybody can be a JavaScript developer.

從在財富500強公司的100多個開發人員團隊中工作的高級工程師到業余時間利用JavaScript編譯器進行黑客攻擊的高中生，任何人都可以成為JavaScript開發人員。

At this point we had two choices:

在這一點上，我們有兩種選擇：

Spend a lot of time and effort trying to define what “the JavaScript ecosystem” means, estimate its total size and make-up, and then compare our results to that figure.
花大量時間和精力來嘗試定義“ JavaScript生態系統”的含義，估計其總大小和組成，然后將我們的結果與該數字進行比較。
Just let any developer take the survey, and present the results as they are without trying to relate them to a larger population.
只需讓任何開發人員參與調查，并按原樣呈現結果，而無需嘗試將它們與更多的人群相關聯。

We simply didn’t have the time or the know-how to go with option 1, so we picked option 2.

我們根本沒有時間或專有技術來解決選項1，因此我們選擇了選項2。

那么誰參加了調查？ (So Who Took the Survey?)

So the natural next question is, who are these developers? This is where we could’ve done a better job. The truth is we had a limited amount of time to process all the data we accumulated, and we decided to focus that time on the actual results themselves rather than on the demographics section.

因此，下一個自然的問題是，這些開發人員是誰？這是我們可以做得更好的地方。事實是，我們只有有限的時間來處理積累的所有數據，因此我們決定將時間集中在實際結果本身上，而不是在人口統計方面。

But since this has come up a few times, I went back and ran a rough aggregation on the self-reported “how did you hear about this survey?” question, coming up with this breakdown:

但是由于這種情況已經發生了幾次，所以我回過頭來對自我報告的“您如何得知這項調查進行粗略的匯總”？問題，提出以下細分：

The number are as follows (out of a total of 20,252 respondents):

人數如下(在總共20,252名受訪者中)：

Email: 2033 respondents (10.04%)
電子郵件 ：2033位受訪者(10.04％)
Twitter: 2062 respondents (10.18%)
Twitter ：2062名受訪者(10.18％)
Reddit: 1043 respondents (5.15%)
Reddit ：1043位受訪者(5.15％)
Slack: 557 respondents (2.75%)
懈怠：557名受訪者(2.75％)
JavaScript Weekly: 529 respondents(2.61%)
JavaScript Weekly ：529位受訪者(2.61％)
Hacker News: 468 respondents(2.31%)
黑客新聞 ：468位回應者(2.31％)
Medium: 285 respondents(1.41%)
中：285位回應者(1.41％)
Facebook: 140 respondents(0.69%)
Facebook ：140位回應者(0.69％)
Other/Unknown: 13272 respondents(65.54%)
其他/未知 ：13272名受訪者(65.54％)

“Email” corresponds to our announcement blast to our own mailing list, which is made up of people who took the survey in previous years and signed up to be kept up to date.

“電子郵件”對應于我們對自己的郵件列表的聲明爆炸，該列表由前幾年參加調查并簽名以保持最新狀態的人員組成。

We also had a field that automatically tracked the browser’s actual referrer value, which works better for some sources but not others (email for example). This lets us get a more granular picture for specific sites:

我們還有一個字段可以自動跟蹤瀏覽器的實際referrer值，該字段對于某些來源(而不是其他來源)(例如電子郵件)效果更好。這使我們對特定站點有了更細致的了解：

推特 (Twitter)

t.co: 1591 respondents.
t.co：1591名受訪者。

谷歌 (Google)

Search: 1591 respondents.
搜索：1591位受訪者。

中 (Medium)

Take the State of JavaScript 2018 Survey! (announcement post published on freeCodeCamp): 3442 respondents.
參加JavaScript 2018狀況調查！ (發布在freeCodeCamp上的公告)：3442名受訪者。
The 12 Things You Need to Consider When Evaluating Any New JavaScript Library (a post I wrote about our question methodology, also published on freeCodeCamp): 105 respondents.
評估任何新JavaScript庫時需要考慮的12件事 (我寫的關于問題方法的文章，也發表在freeCodeCamp上)：105位受訪者。

黑客新聞 (Hacker News)

Frontpage: 634 respondents.
頭版：634名受訪者。

Reddit (Reddit)

State of Javascript 2018 survey is now out (posted on r/javascript): 144 respondents.
Java狀態2018調查現已結束 (發布在r / javascript上)：144位受訪者。

其他論壇 (Other Forums)

Meteor forums: 61 respondents.
流星論壇：61位受訪者。

網志 (Blogs)

State of JavaScript 2018 Survey (Dev.to): 56 respondents.
JavaScript 2018狀況調查 (Dev.to)：56位受訪者。
State of JavaScript 2018' Survey Announced (Slashdot): 219 respondents.
JavaScript 2018的現狀公布的調查 (Slashdot)：219位受訪者。
The Ember Times — Issue №64: 18 respondents.
灰燼時代—第64期：18位受訪者。

As you can see the only sources that might have an inherent bias towards a specific library are the Meteor forums and the Ember Times, and both Meteor and Ember happened to do pretty poorly in the survey.

如您所見，唯一可能對特定圖書館有固有偏見的來源是Meteor論壇和Ember Times，而Meteor和Ember在調查中的表現都很差。

艱難的決定 (Tough Decisions)

I realize that by naming the survey “The State of JavaScript”, we’re staking a claim, and that a non-representative survey would be a problem.

我意識到，通過將調查命名為“ JavaScript狀態”，我們可以提出主張，并且非代表性調查將是一個問題。

So we fully intend to get closer and closer to the “truth” of the JavaScript ecosystem. We know people make decisions based on our research, and we take that responsibility very seriously.

因此，我們完全打算越來越接近JavaScript生態系統的“真相”。我們知道人們會根據我們的研究做出決定，因此我們非常重視這一責任。

At the end of the day, I truly believe the best thing we can do is just keep going, and try to grow the audience year after year. And hopefully, once we get past the 100k respondents milestone (if that ever happens!) we can finally put the representativeness worries to rest.

歸根結底，我堅信，我們能做的最好的事情就是繼續前進，并嘗試逐年增加觀眾。并且希望，一旦我們超過了10萬個受訪者的里程碑(如果有的話！)，我們終于可以消除對代表性的擔憂。

Want to help us make the next State of JS survey even better? Sign up to get next year’s announcement!

是否想幫助我們使下一次JS狀態調查更好？ 注冊以獲取明年的公告！