TIOBE Index for June 2022
June Headline: C++ is about to surpass Java
It seems to be that Java is on the losing side. In April 2020, Java was still number 1 on the TIOBE index. In that same month, Java had to give up its first place to C. Later on, in 2021, Python became unstoppable and surpassed Java as well. Now it looks like C++ is the next language to overtake Java. High level programming with performance is C++'s key reason why it is doing so well. The C++ language is revised every 3 years. Such revisions contain ground-breaking new features, which get the language on par with C# and Java, but without the performance penalty of a garbage collector. Let's see where C++ is heading the next few months. -- Paul Jansen CEO TIOBE Software
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 best programming 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.
|Jun 2022||Jun 2021||Change||Programming Language||Ratings||Change|
|11||11||Classic Visual Basic||1.33%||-0.40%|
Other programming languages
The complete top 50 of programming languages is listed below. This overview is published unofficially, because it could be the case that we missed a language. If you have the impression there is a programming language lacking, please notify us at email@example.com. Please also check the overview of all programming languages that we monitor.
The Next 50 Programming Languages
The following list of languages denotes #51 to #100. Since the differences are relatively small, the programming languages are only listed (in alphabetical order).
- ABC, ActionScript, ATLAS, BBC BASIC, bc, BlitzMax, Bourne shell, CFML, Chapel, CL (OS/400), Clipper, CLIPS, Eiffel, Erlang, EXEC, F#, Forth, Hack, Haxe, Icon, IDL, J#, Ladder Logic, LiveCode, Logo, LPC, Lustre, MDX, MQL4, MUMPS, NATURAL, Nim, Oberon, OCaml, OpenEdge ABL, PostScript, Q, Racket, Raku, REXX, Ring, RPG, Snap!, SPARK, Stata, Tcl, Vala/Genie, VHDL, X10, Xojo
This Month's Changes in the Index
This month the following changes have been made to the definition of the index:
- Peter Villadsen suggested to add Microsoft language X++, which is used to program Microsoft Dynamics. X++ starts at position 49. Thanks Peter!
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.
There are 2 important remarks here:
- There is a difference between "Visual Basic" and "(Visual) Basic" in the table above. Until 2010, "(Visual) Basic" referred to all possible dialects of Basic, including Visual Basic. After some discussion, it has been decided to split "(Visual) Basic" into all its dialects such as Visual Basic .NET, Classic Visual Basic, PureBasic, and Small Basic, just to name a few. Since Visual Basic .NET has become the major implementation of Visual Basic, it is now called "Visual Basic".
- The programming language SQL has not been in the TIOBE index for a long time. In 2018, somebody pointed out that SQL is Turing Complete. From that moment on, SQL is part of the TIOBE index. So although this language is very old, it has only a short history in the index.
Programming Language Hall of Fame
The hall of fame listing all "Programming Language of the Year" award winners is shown below. The award is given to the programming language that has the highest rise in ratings in a year.
Bugs & Change Requests
This is the top 5 of most requested changes and bugs. If you have any suggestions how to improve the index don’t hesitate to send an e-mail to firstname.lastname@example.org.
- Apart from “<language> programming”, also other queries such as “programming with <language>”, “<language> development” and “<language> coding” should be tried out.
- Add queries for other natural languages (apart from English). The idea is to start with the Chinese search engine Baidu. This has been implemented partially and will be completed the next few months.
- Add a list of all search term requests that have been rejected. This is to minimize the number of recurring mails about Rails, JQuery, JSP, etc.
- Start a TIOBE index for databases, software configuration management systems and application frameworks.
- Some search engines allow to query pages that have been added last year. The TIOBE index should only track those recently added pages.
Yes, the only condition is to refer to its original source “www.tiobe.com”.
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 email@example.com.
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 firstname.lastname@example.org for more information.
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.