Let op! Internet Explorer wordt niet meer ondersteund. Hierdoor kan de website mogelijk niet goed functioneren, gebruik een alternatieve browser om optimaal gebruik te maken van deze website. Klik hier om een alternatieve browser te downloaden.

TIOBE Index for June 2025

June Headline: Where is SQL going?

SQL has a remarkable history in the TIOBE index. When the TIOBE index started in 2001, SQL was one of the 20 languages that were tracked. It was a serious top 10 player at that time. In the beginning of 2004, somebody noted that SQL was not a programming language. After lots of debates, it was decided to take SQL from the list. It was in 2018 that somebody else pointed out to us that SQL is Turing complete, albeit in a tricky way. And if you are Turing complete, you are considered to be a programming language. Hence, as of that moment SQL was readded to the TIOBE index and, since databases and SQL go hand in hand, SQL became a top 10 player again.

Remarkably, SQL has started dropping slowly recently. This month it is at position #12, which is its lowest position in the TIOBE index ever. SQL will remain the backbone and lingua franca of databases for decades to come. However, in the booming field of AI, where data is usually unstructured, NoSQL databases are often a better fit. NoSQL (which uses data interchange formats such as JSON and XML) has become a serious threat for the well-defined but rather static SQL approach. NoSQL's popularity is comparable to the rise of dynamically typed languages such as Python if compared to well-defined statically typed programming languages such as C++ and Java.

Author:

Author Paul Jansen

Paul Jansen

Chief Executive Officer Follow Paul Jansen on LinkedIn

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 web sites Google, Amazon, Wikipedia, Bing and more than 20 others 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 2025 Jun 2024 Change Programming Language Ratings Change
11Python pagePython25.87%+10.48%
22C++ pageC++10.68%+0.65%
33C pageC9.47%+0.24%
44Java pageJava8.84%+0.44%
55C# pageC#4.69%-1.96%
66JavaScript pageJavaScript3.21%-0.11%
77Go pageGo2.28%+0.35%
89changeVisual Basic pageVisual Basic2.20%+0.54%
911changeDelphi/Object Pascal pageDelphi/Object Pascal2.15%+0.62%
1010Fortran pageFortran1.86%+0.33%
1125changeAda pageAda1.70%+0.91%
128changeSQL pageSQL1.55%-0.21%
1327changePerl pagePerl1.47%+0.77%
1421changeR pageR1.39%+0.43%
1515PHP pagePHP1.25%+0.03%
1616Scratch pageScratch1.19%+0.02%
1714changeMATLAB pageMATLAB1.13%-0.13%
1817changeRust pageRust0.97%-0.20%
1913changeAssembly language pageAssembly language0.91%-0.35%
2020COBOL pageCOBOL0.89%-0.08%

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 protected]. Please also check the overview of all programming languages that we monitor.

PositionProgramming LanguageRatings
21Classic Visual Basic0.87%
22Prolog0.80%
23Kotlin0.75%
24Ruby0.74%
25Swift0.73%
26SAS0.65%
27Lisp0.57%
28Dart0.50%
29Haskell0.49%
30Lua0.44%
31Scala0.42%
32VBScript0.42%
33Julia0.42%
34Objective-C0.39%
35(Visual) FoxPro0.35%
36GAMS0.30%
37TypeScript0.29%
38PL/SQL0.23%
39ABAP0.23%
40V0.20%
41Solidity0.20%
42D0.19%
43Bash0.18%
44PowerShell0.17%
45ML0.16%
46Elixir0.16%
47Awk0.15%
48X++0.14%
49LabVIEW0.13%
50Erlang0.12%

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).

  • ActionScript, Algol, Alice, Apex, APL, Applescript, CHILL, Clipper, CLIPS, Clojure, Curl, Eiffel, Elm, F#, Forth, Groovy, Hack, Icon, Inform, Io, J, JScript, Ladder Logic, Logo, Maple, Modula-2, Mojo, MQL5, NATURAL, Nim, OCaml, Occam, OpenCL, PL/I, Q, Racket, Ring, RPG, S, Scheme, Smalltalk, SPARK, Stata, Tcl, Transact-SQL, Vala/Genie, VHDL, Wolfram, Xojo, Zig

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 Language202520202015201020052000199519901985
Python137792522--
C++2444321311
Java312123---
C421211211
C#5556109---
JavaScript6789116---
Go71348184-----
Visual Basic81594------
SQL99-------
Fortran103131251619526
PHP12863526---
Ada213530271717693
Lisp27302617158752
Objective-C341431340----
(Visual) Basic--163564344

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 was added to the TIOBE index in 2018 after somebody pointed out that SQL is Turing Complete. 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.

YearWinner
2024medal Python
2023medal C#
2022medal C++
2021medal Python
2020medal Python
2019medal C
2018medal Python
2017medal C
2016medal Go
2015medal Java
2014medal JavaScript
2013medal Transact-SQL
2012medal Objective-C
2011medal Objective-C
2010medal Python
2009medal Go
2008medal C
2007medal Python
2006medal Ruby
2005medal Java
2004medal PHP
2003medal C++

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 [email protected].

  1. Apart from “<language> programming”, also other queries such as “programming with <language>”, “<language> development” and “<language> coding” should be tried out.
  2. 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.
  3. 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.
  4. Start a TIOBE index for databases, software configuration management systems and application frameworks.
  5. 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 protected].

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 [email protected] 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.

Get your own proof of concept

Curious how your projects will be ranked by our TiCS Framework? Request your proof of concept now to discover the quality of your code.

Request a demo