Jump to content

Talk:TIOBE index

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Ideas to add in criticisms section

[edit]

Actually, when you search a topic on Google, it reports at first ranks a lot of aka CV page blog of guys that promote themselves and their pseudo expertise on the topics... cf. Medium etc. Thus, TIOBE measures very well this noise, e.g. it measures for Python all the CV IA guys. Somehow it is trend, but it is over amplified because it doesn't do the job to find the interesting pages on the web.

Moreover, the ranking is a mix of trending and industrial inertia for good or bad reasons. It doesn't provide an analysis on what is going on. For example, Visual Basic is ranked in 2022 between C# and JS with a ranking bump in 2020.

Moreover, it doesn't distinguish between the different sectors, microcontroller IOT, smartphone, desktop, trash programming, high performance software etc. Can we program an uc or OS with VB ? Use asm to code a web app ? Use JS to compute a nuclear bomb ? It mixes SQL, Matlab and Rust in the same bowl.

At last, can we interpret TIOBE Index as a hooking web page for the real Tiobe company business ??? As all these bullshit CV blog pages... — Preceding unsigned comment added by 2A01:CB00:979:6A00:B015:318A:B007:6106 (talk) 17:45, 27 October 2022 (UTC)[reply]

Flawed analysis

[edit]

Flawed. You can't just base language popularity by search engine since not all languages are easily available to the general public. Especially high-end development environments which can only be obtained thru corporate-sponsored training and provisioning. 64.114.212.6 (talk) 20:57, 5 November 2009 (UTC)YvrAnalyst[reply]

From the other side, languages that are only available to elite are unlikely to be popular between the wide public, this is that the index shows. It does not show absolute value of the language, amount of money involved in development around it or something the like. Audriusa (talk) 15:10, 7 May 2010 (UTC)[reply]
I use google search when I want to solve a problem when programming; so I think the most searched language is the one that has the more problems/bugs to solve. --Agreppin (talk) 15:11, 29 July 2010 (UTC)[reply]
Or it could be that problems/bugs in more popular languages are noticed more often and by more people than problems in less popular ones. --Joshua Issac (talk) 22:39, 14 August 2010 (UTC)[reply]
Yes, I agree. A point of view as many sides. --Agreppin 15 Nov 2010 —Preceding undated comment added 00:57, 15 November 2010 (UTC).[reply]
Irrelevant. Everything in IT is flawed. Some measure of language popularity is useful; this is the best one I know of; if you have a better idea, tell us, and maybe someone will implement it. Longitude2 (talk) 08:57, 16 September 2020 (UTC)[reply]

Acronym

[edit]

What does TIOBE actually stand for, as an acronym? Jubal Kessler (talk) 17:57, 6 September 2011 (UTC)[reply]

Asked and answered— it's in the article and the company's website. This might be their response to Don't be evil. WurmWoodeT 19:02, 25 July 2017 (UTC)[reply]

Criticism

[edit]

This article clearly lacks such section.

Suppose, Blahblahsoft Coproration releases new release of their Superduper Studio Professional Enterprise Edition with broken documentation system (quite possible case!), effectively forcing their users to resort to the on-line version of docs, searchable via Poople Inc. It will boost their trends accordingly, and (voila!) TIOBE's "popularity" metric grows, while in reality such a case caused notable percent of users to leave.

If Transact-SQL is the "language of the year", then something is wrong with Tiobe Index. We know what the commonly used languages are, such as C, C++, Objective C, C#, Java, JavaScript, and PHP. Tiobe Index does catch all of those, but that is no great accomplishment. It falls prey to statistical fallacies and variations due to methodology changes, and ends up with a silly conclusion that Transact-SQL is "language of the year". 71.212.48.92 (talk) 05:59, 13 January 2014 (UTC)[reply]
http://www.tiobe.com/index.php/content/paperinfo/tpci/Transact_SQL.html - It's interesting that five months after Transact-SQL is "language of the year", it is "back in the doldrums". I have nothing against Transact-SQL, it's just the innocent bystander here. Supposedly, in 2013, Transact-SQL zoomed in popularity from 0.5% to 2.5%, fortuitously peaking at or near the time of judging for "language of the year". Since then, in 2014, it has supposedly plummeted in popularity, returning back to the 1% level by May, 2014. The TIOBE Index has some relationship to popularity, but there seems some very large artifact going on with the methodology. Otherwise, what might the explanation that Transact-SQL supposedly radically changed in popularity, zooming up and then plummeting, within 20 months? I think this might be reflected some in the article. 71.217.113.212 (talk) 17:19, 7 May 2014 (UTC)[reply]
https://www.tiobe.com/tiobe-index/c/ - 11/7/2015 - 17.15% popularity. 5/6/2017 - finished dropping to 7% popularity. 9/3/2018 - finished zooming back up to 15.45% popularity. Really? Does not make sense. Coincident with all the volatility, C was named "language of the year", which might be named "most volatile language of the year". With rare exceptions, computer languages do NOT undergo radical changes in popularity over a one year period. There are obviously artifacts going on. I think this should be addressed some in the article. TIOBE Index is useful on a gross level, but obviously flawed. 71.212.115.192 (talk) 04:58, 21 March 2021 (UTC)[reply]

Who owns TIOBE?

[edit]

I was expecting some data as to who owns TIOBE and where it resides. Perhaps the article could state so, in an objective and neutral manner. 2A02:8388:1600:C80:BE5F:F4FF:FECD:7CB2 (talk) 15:46, 5 August 2016 (UTC)[reply]

Where = Eindhoven in the first line, but who = who knows synspace might not pass WP:42.2A03:2267:0:0:FCFA:27FC:EA8D:246B (talk) 16:15, 20 January 2017 (UTC)[reply]

This has since been added to TIOBE's about page. LCMJansen (talk) 07:49, 20 July 2021 (UTC)[reply]