原文：
TIOBE Index for November 2018
November Headline: the programming language of 2018 will be one of the top languages
There are only 2 months left before TIOBE will announce the programming language of the year 2018. There appear to be 5 candidates and these are all from the top 5: Java, C, C++, Python and Visual Basic .NET. Every year we hope that some shiny new programming language wins the award but for 2018 it will most probably be a well established language. There are new programming languages, but they just gain too few tration to deserve the title “programming language of the year”. For instance, Apex jumped from position 46 to 36 last month, whereas Alice went from position 62 to 44 in the same time period. But these are all background battles, because both languages gained less than 0.5% in 2018. Let’s see what language is going to win.
IMPORTANT NOTE. SQL has been added again to the TIOBE index since February 2018. The reason for this is that SQL appears to be Turing complete. As a consequence, there is no recent history for the language and thus it might seem that the SQL language is rising very fast. This is not the case.
The TIOBE Programming Community index is an indicator of the popularity of programming languages. The index is updated once a month. The ratings are based on the number of skilled engineers world-wide, courses and third party vendors. Popular search engines such as Google, Bing, Yahoo!, Wikipedia, Amazon, YouTube and Baidu are used to calculate the ratings. It is important to note that the TIOBE index is not about the bestprogramming language or the language in which most lines of code have been written.
The index can be used to check whether your programming skills are still up to date or to make a strategic decision about what programming language should be adopted when starting to build a new software system. The definition of the TIOBE index can be found here.
世界级编程语言排行榜前20名
| Nov 2018 | Nov 2017 | Change | Programming Language | Ratings | Change |
|---|---|---|---|---|---|
| 1 | 1 | Java | 16.746% | +3.51% | |
| 2 | 2 | C | 14.396% | +5.10% | |
| 3 | 3 | C++ | 8.282% | +2.94% | |
| 4 | 4 | Python | 7.683% | +3.20% | |
| 5 | 7 |  |
Visual Basic .NET | 6.490% | +3.58% |
| 6 | 5 |  |
C# | 3.952% | +0.94% |
| 7 | 6 | |
JavaScript | 2.655% | -0.32% |
| 8 | 8 | PHP | 2.376% | +0.48% | |
| 9 | – |  |
SQL | 1.844% | +1.84% |
| 10 | 14 | |
Go | 1.495% | -0.07% |
| 11 | 19 | |
Objective-C | 1.476% | +0.06% |
| 12 | 20 | |
Swift | 1.455% | +0.07% |
| 13 | 9 |  |
Delphi/Object Pascal | 1.423% | -0.32% |
| 14 | 11 | |
R | 1.407% | -0.20% |
| 15 | 10 | |
Assembly language | 1.108% | -0.61% |
| 16 | 13 | |
Ruby | 1.091% | -0.50% |
| 17 | 12 | |
MATLAB | 1.030% | -0.57% |
| 18 | 15 | |
Perl | 1.001% | -0.56% |
| 19 | 18 | |
PL/SQL | 1.000% | -0.45% |
| 20 | 17 | |
Visual Basic | 0.854% | -0.63% |
This Month’s Changes in the Index
This month the following changes have been made to the definition of the index:
- There are lots of mails that still need to be processed. As soon as there is more time available your mail will be answered. Please be patient.
Very Long Term History
To see the bigger picture, please find below the positions of the top 10 programming languages of many years back. Please note that these are average positions for a period of 12 months.
| Programming Language | 2018 | 2013 | 2008 | 2003 | 1998 | 1993 | 1988 |
|---|---|---|---|---|---|---|---|
| Java | 1 | 2 | 1 | 1 | 17 | – | – |
| C | 2 | 1 | 2 | 2 | 1 | 1 | 1 |
| C++ | 3 | 4 | 3 | 3 | 2 | 2 | 4 |
| Python | 4 | 7 | 5 | 10 | 24 | 18 | – |
| C# | 5 | 5 | 7 | 8 | – | – | – |
| Visual Basic .NET | 6 | 11 | – | – | – | – | – |
| PHP | 7 | 6 | 4 | 5 | – | – | – |
| JavaScript | 8 | 9 | 8 | 7 | 22 | – | – |
| Ruby | 9 | 10 | 10 | 18 | – | – | – |
| Swift | 10 | – | – | – | – | – | – |
| Objective-C | 14 | 3 | 40 | 49 | – | – | – |
| Perl | 16 | 8 | 6 | 4 | 3 | 11 | 22 |
| Lisp | 29 | 12 | 16 | 13 | 8 | 6 | 2 |
| Ada | 31 | 19 | 19 | 15 | 12 | 5 | 3 |
| Pascal | 187 | 14 | 14 | 96 | 4 | 3 | 13 |
Frequently Asked Questions (FAQ)
- Q: Am I allowed to show the TIOBE index in my weblog/presentation/publication?A: Yes, the only condition is to refer to its original source “www.tiobe.com”.
- Q: How may I nominate a new language to be added to the TIOBE index?A: If a language meets the criteria of being listed (i.e. it is Turing complete and has an own Wikipedia entry that indicates that it concerns a programming language) and it is sufficiently popular (more than 5,000 hits for +”<language> programming” for Google), then please write an e-mail to tpci@tiobe.com.
- Q: I would like to have the complete data set of the TIOBE index. Is this possible?A: We spent a lot of effort to obtain all the data and keep the TIOBE index up to date. In order to compensate a bit for this, we ask a fee of 5,000 US$ for the complete data set. The data set runs from June 2001 till today. It started with 25 languages back in 2001, and now measures more than 150 languages once a month. The data are available in comma separated format. Please contact sales@tiobe.com for more information.
- Q: Why is the maximum taken to calculate the ranking for a grouping, why not the sum?A: Well, you can do it either way and both are wrong. If you take the sum, then you get the intersection twice. If you take the max, then you miss the difference. Which one to choose? Suppose somebody comes up with a new search term that is 10% of the original. If you take the max, nothing changes. If you take the sum then the ratings will rise 10%. So taking the sum will be an incentive for some to come up with all kinds of obscure terms for a language. That’s why we decided to take the max.
The proper way to solve this is is of course to take the sum and subtract the intersection. This will give rise to an explosion of extra queries that must be performed. Suppose a language has a grouping of 15 terms, then you have to perform 32,768 queries (all combinations of intersections). So this seems not possible either… If somebody has a solution for this, please let us know.
- Q: What happened to Java in April 2004? Did you change your methodology?A: No, we did not change our methodology at that time. Google changed its methodology. They performed a general sweep action to get rid of all kinds of web sites that had been pushed up. As a consequence, there was a huge drop for languages such as Java and C++. In order to minimize such fluctuations in the future, we added two more search engines (MSN and Yahoo) a few months after this incident.
——顾亚恒网站注明：以上数据版权归TIOBE所有
