Translate finished

This commit is contained in:
eric.xiaozhen 2016-09-08 15:15:19 +08:00
parent b6f74e7811
commit 795035082e
2 changed files with 99 additions and 104 deletions

View File

@ -1,104 +0,0 @@
Eriwoon 认领翻译
The State Of JavaScript: JavaScript Flavors
===========
One thing that distinguishes JavaScript from other programming languages is that JavaScript isnt just one language: its actually more like a family of closely related cousins.
What started with CoffeeScript back in 2009 has become an explosion of choice over the past couple years: ES6, TypeScript, Elm… they all have their strengths, and they all compile down to good old JavaScript.
So after last weeks look at front-end frameworks, lets look at what the State Of JavaScript survey can tell us about JavaScript Flavors.
Disclaimer: these are preliminary results extracted from a partial dataset. Theyre just a way for me to share some insights while I take my time to come up with the best way to present the complete results.
Note: if you havent taken the survey yet, now would be the perfect time to do it! Itll only take 10 minutes and you can come back here after :)
### Awareness
First, I wanted to find out the percentage of respondents that were aware of each of the six options existence:
- Good Old Plain JavaScript: 97%
- ES6: 98%
- CoffeeScript: 99%
- TypeScript: 98%
- Elm: 66%
- ClojureScript: 77%
You would expect that “Good Old Plain JavaScript” would score 100% awareness, but I imagine some people couldnt resist the temptation of picking “Ive never heard of JavaScript” in a JavaScript survey…
ES6, CoffeeScript, and TypeScript all have near-perfect awareness, which surprised me since TypeScript isnt quite as widespread as the other two.
Elm and ClojureScript on the other hand have much lower scores, which makes sense since theyre more tied to their own ecosystems, and harder to use in existing apps.
### Interest
Next, lets look at which flavors have been generating the most interest among developers who havent used them yet:
![](https://embed.chartblocks.com/1.0/?c=57c4dc599973d2525fee820a&referrer=https%3A%2F%2Fmedium.com%2Fmedia%2F63092db0523a37d9d33ce6c014d727f6%3FmaxWidth%3D700&t=3efc9491eba2ce2#)
Remember were looking at non-users here, so it makes sense that there would be very few people who havent used Plain JavaScript.
Its interesting to look at ES6: a large proportion of developers have already jumped on the bandwagon, and almost all (89%) of those who havent yet want to learn it as well.
TypeScript and Elm are in the same boat: not many people have used them, but they have 53% and 58% interest scores respectively, which isnt bad by any means.
If I had to guess, Id say that both TypeScript and Elm might be having a hard time articulating their advantages to the average JavaScript developer. After all its hard to understand the advantages of something like static typing if all you know is JavaScript.
Also, few developers have used CoffeeScript, and apparently almost nobody wants to learn it. There goes my plan to write a 12-volume CoffeeScript Encyclopedia…
### Satisfaction
We now come to the key question: how many developers have used each specific flavor, and how many would use it again?
![](https://embed.chartblocks.com/1.0/?c=57c4e5f79973d29461ee820a&referrer=https%3A%2F%2Fmedium.com%2Fmedia%2F1fe4bbdf807f87883fa108e31c6927d5%3FmaxWidth%3D700&t=1061d2ab8fc9838#)
While plain JavaScript has larger usage numbers as expected, in terms of satisfaction the big winner here is ES6, and I think its safe to say its now the default way to write JavaScript apps.
TypeScript and Elm both also have similarly high satisfaction percentages, around 85%. And once more, poor CoffeeScript trails the poll with only 17% of developers willing to consider it again.
### Happiness
Finally, I asked people how happy they were with their current way of writing JavaScript:
![](https://embed.chartblocks.com/1.0/?c=57c4cd8c9973d2d95bee820a&referrer=https%3A%2F%2Fmedium.com%2Fmedia%2F538138b2d91d1fa99f1696bef4dd4d3f%3FmaxWidth%3D700&t=f53efb029ea4456#)
The high scores we saw in the previous question are confirmed here: with an average score of 3.96 overall, people are really happy with JavaScript as a language.
Its hard to say if this is because of JavaScripts recent improvements, or because maybe (just maybe) JavaScript isnt as horrible a language as people make it to be. But its certainly comforting.
### Conclusions
If React and Vue were the clear winners last time, I would say that here its without a doubt ES6. This is not groundbreaking news by any means, but its nice to know the community is embracing the direction the language is taking.
It will be really interesting to ask these questions again a year or so from now, and see if TypeScript, Elm, and ClojureScript have made any progress.
Personally, I suspect this explosion of flavors is just the beginning, and that the way we write JavaScript a couple years from now might be quite different!
### Share the Word & Stay Tuned
When it comes to surveys like this one, more data equals better data! The more people take the survey, the more representative of the overall JavaScript community it will be.
So if you can, I encourage you to share the survey:
[On Twitter][1]
[On Facebook][2]
And if youd like to know next time I publish results, [head to the survey homepage][3] and leave your email there to be notified!
--------------------------------------------------------------------------------
via: https://www.oreilly.com/ideas/spark-comparison-aws-vs-gcp?utm_source=dbweekly&utm_medium=email
作者:[Sacha Greif][a]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://medium.com/@sachagreif
[1]: https://twitter.com/intent/tweet/?text=The%20State%20Of%20JavaScript%3A%20take%20a%20short%20survey%20about%20popular%20JavaScript%20technologies%20http%3A%2F%2Fstateofjs.com%20%23stateofjs
[2]: https://facebook.com/sharer/sharer.php?u=http%3A%2F%2Fstateofjs.com
[3]: http://stateofjs.com/

View File

@ -0,0 +1,99 @@
JavaScript 现状:方言篇
===========
JavaScript 和其他编程语言有一个很大的不同,它不像单纯的一个语言,而像一个由众多方言组成大家族。
从2009年 CoffeeScript 的出现开始,近几年出现了大量基于 JavaScript 语言,或者叫方言,例如 ES6TypeScriptElm 等等。它们都有自己的优势,且都可以被完美编译成标准 JavaScript。
所以,继上周的前端框架篇,今天带来 JavaScript 现状之方言篇,看一下大家对于 JavaScript 的方言是怎么选择的。
> 声明:下面的结论是根据部分数据得出的初步结果,希望能将我的一些想法带给大家,对于完整数据后面我会用更好方式呈现出来。
> 注意:如果你还没有参与这个调查,现在就来参加吧,可以花十分钟完成调查然后再回来看这篇文章。
### 认知度
首先,我想看一下参与问卷调查的人是否**知道**下面六种语言:
- 经典的 JavaScript: 97%
- ES6: 98%
- CoffeeScript: 99%
- TypeScript: 98%
- Elm: 66%
- ClojureScript: 77%
你可能觉得100%的人都应该知道『经典的 JavaScript 』,我想是有人无法抵抗『我从来没有听说过 JavaScript 』这个选项的强大诱惑吧……
几乎所有人都知道 ES6、CoffeeScript 和 TypeScript 这三种语言,比较令我惊讶的是 TypeScript 竟然会稍微落后于 ES6 和 CoffeeScript。
另一方面Elm 和 ClojureScript 得分就要低得多,当然这也有道理,因为它们跟自己的生态环境绑定的比较紧密,也很难在已有的 App 中进行使用。
### 兴趣度
接下来,让我们一起看一下,哪一种方言吸引新开发者的能力更强一些:
![](https://d3ugvbs94d921r.cloudfront.net/57c4dc599973d2525fee820a.png?t=3efc9491eba2ce2)
要注意,表是统计该语言对从未使用过它们的用户的吸引度,因为只有很少人没有用过经典 JavaScript所以『经典 JavaScript 』这一列的数值很低。
ES6的数值很有趣已有很大比例的用户在使用 ES6 了没有用过的人中的绝大部分89%)也很想学习它。
TypeScript 和 Elm 的状态差不多:用过的人不多,但感兴趣的比例表现不错,分别是 53% 和 58%。
如果让我预测一下,那我觉得 TypeScript 和 Elm 都很难向普通的 JavaScript 开发者讲明自己的优势。毕竟如果开发者只懂 JavaScript 的话,你很难解释清楚静态类型的好处。
另外,只有很少开发者用过 CoffeeScript而且很明显几乎没人想去学。我觉得我该写一本 12 卷厚的 CoffeeScript 百科全书了……
### 满意度
现在是最重要的问题的时间了:有多少开发者用过这些语言,有多少人还想继续使用这些方言呢?
![](https://d3ugvbs94d921r.cloudfront.net/57c4e5f79973d29461ee820a.png?t=1061d2ab8fc9838)
虽然经典 JavaScript 拥有最多的用户量,但就满意度来说 ES6 才是大赢家而且我想现在已经能安全的说ES6 可以作为开发 JavaScript App 默认的语言。
TypeScript 和 Elm 有相似的高满意度,都在 85% 上下。然后,只有可怜的 17% 的开发者会考虑继续使用 CoffeeScript。
### 快乐度
最后一个问题,我问大家在用现在的方式写 JavaScript 时是否感到快乐:
![](https://d3ugvbs94d921r.cloudfront.net/57c4cd8c9973d2d95bee820a.png?t=f53efb029ea4456)
这个问题的答案和上一个问题的满意度想匹配:平均分达到 3.96 分1 - 5 分),大家在使用 JavaScript 时候确实是快乐的。
不过很难说高分是因为 JavaScript 最近的一些改进造成的呢,还是发现 JavaScript 可能仅仅是可能没有大家认为的那么讨厌。总之JavaScript 令人满意。
### 总结
如果说上次的赢家是 React 和 Vue那此次调查的冠军毫无争议是 ES6 了。 ES6 并带来没有开天辟地的变化,但整个社区都还是很认可当前 JavaScript 演进方向的。
我觉得一年之后我们再来一次这样的调查,结果会很有趣。同时也可以关注一下 TypeScript、Elm 还有ClojureScript 有没有继续进步。
个人认为,当前 JavaScript 大家庭百花齐放的现象还只是一个开始,或许几年之后 JavaScript 就会变得非常不同了。
### 结语&敬请期待
对于我这样的调查来说数据越多就意味着数据越准确!越多人参加这个调查,那就越能代表整个 JavaScript 社区。
所以,我十分希望你能帮忙分享这个调查问卷:
[On Twitter][1]
[On Facebook][2]
另外,如果你想收到我下一个调查结果分析,前往 [调查问卷主页][3] 并留下自己的邮箱吧。
--------------------------------------------------------------------------------
via: https://www.oreilly.com/ideas/spark-comparison-aws-vs-gcp?utm_source=dbweekly&utm_medium=email
作者:[Sacha Greif][a]
译者:[eriwoon](https://github.com/eriwoon)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://medium.com/@sachagreif
[1]: https://twitter.com/intent/tweet/?text=The%20State%20Of%20JavaScript%3A%20take%20a%20short%20survey%20about%20popular%20JavaScript%20technologies%20http%3A%2F%2Fstateofjs.com%20%23stateofjs
[2]: https://facebook.com/sharer/sharer.php?u=http%3A%2F%2Fstateofjs.com
[3]: http://stateofjs.com/