The 2018 Top Programming Languages, According To IEEE (ieee.org)
New submitter rfengineer shares a report: Welcome to IEEE Spectrum's fifth annual interactive ranking of the top programming languages. Because no one can peer over the shoulders of every coder out there, anyone attempting to measure the popularity of computer languages must rely on proxy measures of relative popularity. In our case, this means combining metrics from multiple sources to rank 47 languages. But recognizing that different programmers have different needs and domains of interest, we've chosen not to blend all those metrics up into One Ranking to Rule Them All. [...] Python has tightened its grip on the No. 1 spot. Last year it came out on top by just barely beating out C, with Python's score of 100 to C's 99.7. But this year, there's a wider gap between first and second place, with C++ coming in at 98.4 for the No. 2 slot (last year, Java had come third with a score of 99.4, while this year its fallen to 4th place with a score of 97.5). C has fallen to third place, with a score of 98.2.
No.
Maybe to people learning programming and trying to decide what they should focus on so as to be relevant when they graduate.
By the time they graduate, all the languages-du-jour will have changed.
The only things that will always be there are assembly, C, C++, javascript*.
* until all the major browsers switch to something else, but they'll never agree to that.
#DeleteFacebook
From the TFA of TFA of TFA:
"one less source this year, as the Dice job site shut down its API"
(https://spectrum.ieee.org/static/interactive-the-top-programming-languages-2018)
And likely creating all the security holes that make the internet the wild, wild west that it is. Thanks bud.
If anything this list proves that the languages du-jour aren't actually very popular and people tend to stick with the decades old ones.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Does python have rockstars? Does C++ have ninjas? Does java have 10x rockstar ninja? No!
Javascript is a 10x rock star ninja. One moment, you're sitting there, alive, than POW you're dead. And there's an asian guy with playing some sweet riffs on his guitar/sword, teabagging your mouth.
And if you're only a 1xer, that's cool too. npm has tons of high quality javascript one-liners written by the industries best 10xer and/or bootcamp homework projects. How do you know if something is the number 3 in c++? You don't! But npm has probably 30 or 50 packages to check for the number 3.
Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
I do not like your hat.
> So what are the Top Ten Languages of 2018, as ranked for the typical IEEE member and Spectrum reader?
Their membership must be a very niche market for R to outrank JavaScript in "popularity".
The article admits that different languages are used for different things. It's like making a list of "top vehicles", including cars, trucks, ferries, cargo container ships, and airplanes. Yet they go right ahead and still create a master ranking, because they can't help themselves. And we can't help but froth about it, which is the entire damn point for all of this.
It's hard to get too frothy when my own language of choice, C++, is near the top, but my own view tends to be incredibly myopic, as I work in the game industry, and C++ absolutely dominates there.
Irony: Agile development has too much intertia to be abandoned now.
Yes, this is yet another "What's the best/most popular Programming Language" and I suspect that for most people, it's not very representative.
But, as an EE I can see that this list (especially the top ten) is very accurate for the development work that I do (embedded and web apps accessing the embedded devices) and I suspect that it's pretty good for other EEs.
If you're a web, app, database developer or even involved in IT, this list will NOT be accurate.
Mimetics Inc. Twitter
If it's in the top 5 or 6 now and had been holding steady or climbing for the last couple of years it's hard to imagine that it wouldn't still be in the top 10 in a few years.
Most of the things in the top 10 list of 2018 have been around and popular for a decade at least. The exception would be Go which is only 9 years old.
And likely creating all the security holes that make the internet the wild, wild west that it is. Thanks bud.
Handing a good language to a bad coder doesn't result in better code. I've seen plenty of security holes in any language.
The take the list from each year for the past 40 years and graph (or animate) the rise and fall of each language over time. It should be pretty obvious which languages stick around long term, and which ones come and go, and of those that come and go, what trends they have in common.
ok kids, it is up to you to save Forth. I don't see why so many people use assembly on embedded systems when it is easy to develop a customized Forth evvironment.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
Look at those dogs go. GO DOGS GO!
...when everything is a crime, everyone is a criminal.
https://www.tiobe.com/tiobe-in...
https://insights.stackoverflow...
One thing a list like this is helpful for is anyone looking to learn a new language, or learning programming or computer science without prior experience... if your school is teaching their mainline classes in a language not on this list, that is a major red flag. Probably should be in the top 5, to be honest, given what's in the 6-10 slots.
Or, if you don't really know what you're looking to get into, other than being able to make your computer do stuff, then this might be a good guide. Start by defining the type of programming that interests you, then look at this list for the best-in-class option(s). A seasoned programmer looking for a change of pace would do worse than to pick up one of the others on this list-- just for the paradigm shifts and being forced to exercise a bit differently.
I mean, I do see some "not-on-your-life" languages in the list, especially PHP. But given the apparent demand, even that might be a good way to break into the industry for a later-life career change for someone with a technical bent. Something to do for ten years until retirement kind of thing.
I do not have a signature
* until all the major browsers switch to something else, but they'll never agree to that.
They already did! It's called webassembly. :-) There's probably 10 languages that compile down to it now.
I'm being a bit tongue-in-cheek here. It will be a while before developers start switching and we will see what they move to. Probably decades before javascript seriously wanes. It could even get good in the mean time. But the path is open now.
Yes, engineers instead of script kiddies.
AaaaahahahaHAHAHA!
Well at least we have sex on a regular basis and get to go home when workhours end. And I also hear a little envy in there, over the fact that "script-kiddies" get more done in 3 months with their Plone Appserver / CMS than you Java/C++/C/Whatever lot in 5 years. But hey, at least you have neat specs!
We suffer more in our imagination than in reality. - Seneca
BOW DOWN MORTALS Before the one true language. The Ur-language that ushers in all the false idols. The Most Holy of relics...
C
The old gods are calling. Can you hear them? It's the sound of inevitability as the young usurpers weep into their transient drinks feeling their lifeblood leak away like so much memory. What pidly followers they amassed will blow away like so much dust. And where do they turn when all they hold dear is cast about on shifting sands? The stable bedrock of C.
LOOK UPON IT'S MAJESTY and look upon your EVERYTHING and you will see it staring back at you. Your Linux, your arduinos, your Rasberry Pis, your toaster, your fridge. We are the ones who cook your food. We are the ones who drive your cars. We are the ones who hand-carry your garbage when your program closes. DO NOT fuck with us.
Just high enough above the metal to be portable as all fucking get out and low enough slide through that silicon like greased lightning. This IS your grand-daddies programming language because he knew his shit. The experience of GENERATIONS is out there and honestly eager to help. Ask on stack overflow about how the shareponit widget gets shuffled by the flub API in the .WHORE framework and you'll have a couple crickets for company. But ask for some fluent C and the fucking CHOIR comes out to play.
C is the language to learn my friends. It gets you where you need to be. It's not the last language you want to learn, but it's certainly the one you want to sharpen. Hone that to a razor edge and you can cut any problem down to size. And that's no Turing tarpit. I may program in Brainfuck and Malbolge for shits'n'giggles, but C is the workhorse of solving real meaningful problems. Bash glues yesterday's solutions together, and some pretty GUI-maker can make yet another button for a clueless suit, but you whip out C for the hard cases.
#include
int main(int argc, char** argv)
{
printf("Bro, do you even code?\n");
return 0;
}
Negative. Most C programmers avoid web-coding and phone-coding like the plague. Those are shitty low-rent jobs for teenagers and Indians.
I'd start counting flaws but I don't have all day. At least these are readily apparent.
HTML is not a programming language. It's a markup language, and although one might be able to coerce HTML5 and CSS3 together into being Turing complete that's an emergent property best thought of as a bug.
SQL is a query language. Fairly sophisticated data manipulations can be done with it, but it's typically used with an actual programming language to develop applications.
Arduino isn't a language at all. It's a hardware device which can be programmed in various languages. There is an approved IDE but more than one language supports the platform.
Cuda is not a language, but a toolkit for GPU programming that's used from multiple different languages.
Shell and assembly are each more than one language. May as well by that logic call Clojure, Scheme, and Racket part of Lisp. Call JavaScript and ActionScript both ECMAScript.
The method of looking at searches for "X programming" specifically gives an advantage to languages that don't lend themselves to search or need disambiguation like C, Go, Python, Ruby, R, S, D, shell, assembly, or Crystal. Languages with distinct names like Perl, Erlang, JavaScript, Smalltalk, ActionScript, or Matlab don't generally need such qualification.
Actually, I hate C because it's so difficult to send data between executing parallel processes and, secondarily, because it such a beast to handle unicode in. C was probably my third programming language, and the second was assembler. (Fortran was my first.) There are a few other reasons, the dangerous way it handles pointers, etc., and it's ugly when you start needing multiple layers of indirection. But most of those can be gotten used to. The first two, however, ... shudder...
I think we've pushed this "anyone can grow up to be president" thing too far.
C++ is a pretty good language. It's main problem is it's trying to be the five top languages. Just about nobody uses more than a small subset of C++ plus the underlying commonality of C (with, admittedly a dialect difference from standard C).
The problem with this is that it makes all the features obnoxiously ugly, because it really needs to squirm to maintain compatibility with all the features when it wants to handle something new.
E.G.: I want a language with a built-in garbage collector and hash tables. This is because of the area in which I'm working. It means that C++ is uses really annoying syntax and I need non-standard libraries. So I look elsewhere. But if I were already committed to C++, I *could* do the entire thing in it, and it could be just as efficient, possibly more so. BUT it would be extremely ugly and difficult to maintain.
I think we've pushed this "anyone can grow up to be president" thing too far.
and its marketing of it?
Running with Linux for over 20 years!
No, a good language with a strong compiler keeps mediocre developers from continuing to make rookie mistakes because they were running on autopilot.
It also lets great developers to stop worrying about boilerplate and focus on pure function. That's the whole point why you build around frameworks...so you put the drudgery to the side and just do the work that needs to be done.
You will always have sloppy, bad developers who will continue to build houses of cards and Christmas trees that come down with the slightest bit of stress. And dev teams should continue to work hard to weed these individuals out of their ranks.
And likely creating all the security holes that make the internet the wild, wild west that it is. Thanks bud.
The security holes that matter on the internet are XSS and SQL injection. C is entirely innocent of the former, and rarely in the latter It's been many years since buffer overruns and the like were real security issues on the internet.
Socialism: a lie told by totalitarians and believed by fools.
I would expect some volatility here ... but this article makes it sound like the two most used languages can be one thing last year and completely different languages the next.
... esp those over 35.
A change of that size and speed would have a lot of jarring ripples that ordinary developers would probably notice. I'm a little skeptical here.
And it matters a lot for any devs hoping to stay in tech
SQL is Turing complete. Which is somewhat terrifying, but far less so than C++ template meta-programming (talk about an emergent property best thought of as a bug!).
Socialism: a lie told by totalitarians and believed by fools.
I'm both a developer and I hire developers. For anyone trying to figure out which language to learn, I can tell you I hate to hire the ones for the top languages because they are so in demand.
Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
C was the first modern language I learned (though I may be showing my age) and I liked it fine. If you really need the speed and control that's the way to go. It would be terrible for a web framework though. You might squeak out a little bit more performance with C but you're going to cost yourself a lot of time coding those details. If I just want to make a page that displays a table with some options today, and then add more options tomorrow, and then add a detail page with the options, high level is the way to go.
Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
That it is, but it's not generally used to develop actual standalone software. Apart from the odd one-off ad hoc query it's wrapped by another language and often has a stored procedure or several in another (possibly different still) language.
Actually, I hate C because it's so difficult to send data between executing parallel processes and, secondarily, because it such a beast to handle unicode in.
You handle unicode internally by using one of the many many libraries to turn UCS-2, wchar_t and UTF-16 into UTF-8, and then proceed as normal.
Those same libraries usually let you turn UTF-8 back into UCS-2, wchar_t and UTF-16.
Honestly, you only have unicode problems if you're programming on Windows.
You forgot Bourne shell script... 30 years of observing the world says that everything will be rewritten into one of those five, unless it is already 20 years old and in Fortran or Cobol, in which case someone will keep it going, because they are too scared to rewrite it.
Keep in mind that an awful lot of meaningful programming is done by folks who are capable, but are not "computer scientists" They tend to prefer "scripting languages" (Python, Perl, Javascript). to glorified assembly languages. But even though they don't and maybe can't write device drivers, their needs and preferences are important too.
If you're trying to make sense of 10 million data points, do you really want to write a C++ program to filter, manipulate, join sets, etc. Probably not. Even if you can do C or C++ or assembler, in practice, you'll probably use R or mathlab or Python.
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
I actually worked with those old 20000 line plus Fortran programs and they were surprisingly easy to work with. One quickly learned that in order to maintain some semblence of sanity, one had to block line numbers by function -- e.g. 0-1000 are global stuff, 1000-2000 are input ... Sounds dumb, but it worked. In a few cases I saw both the 1960s monolithic Fortran code and the 1980s modern style code with roughly sixteen zillion tiny subroutines. Personally, I think the older style was often easier to work with.
I don't know much about Cobol, but the one time I had to debug an issue in a Cobol subsystem, I found it to be surprisingly readable. I don't think I have the patience to write Cobol code, but I think it probably deserves more respect than it gets.
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
"Like the actual hardware doesn't have flaws as well.. Intel.."
Personally, I think the Intel x86 instruction set is all the evidence that anyone could need that being utterly and completely incompetent is not an imprediment to achieving overwhelming success. Even at the 8088 level it was a shambles compared to say the Motorola 6809. And it has only gotten worse over time.
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
Interesting thought -- seriously. Back around 1980 or so, I decided that if I was going to be doing computer stuff for most of my career, I should learn the basics, so I read Hamming, and Knuth and Tannenbaum and Dijkstra and ...
All the important books and papers available at the time I think
I came away with the feeling that there were solid pieces of foundation here and there. But no body of knowledge that constituted a "science". My feeling is that things haven't really changed all that much. But what the hell do I know?
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
The comment about non-standard libraries was WRT garbage collection.
I think we've pushed this "anyone can grow up to be president" thing too far.
Funny enough, I've seen people write terribly complex 'scripting' code that is clearly more sophisticated than a lot of C programmers, and yet the people writing that will still be intimidated by a compiled language.
Also seen it in shell scripting. People who go through pretty tortuous stuff to make complex code in shell script, but won't even touch python or perl or anything like that, because *that* would be programming, and they don't feel like they could 'program', despite already programming heavily..
XML is like violence. If it doesn't solve the problem, use more.
Python is a pretty advanced language. I don't use it much but it's not at all like the Python from the 90s. The only thing really stopping it from being "mature" is that version 2 and 3 are incompatible. I whipped up a simulator for a board with it so we could work with it before the board was ready, and no way could I have done this with C without adding a few months effort, and easier than Perl even though I know Perl better than Python.
Lisp is a great language. It's probably too abstract for some people though.
Use UTF-8 and it's trivial in C. Can use all the normal string functions unlike the abomination of wide characters. The only time you need to convert a multibyte format into a fat character format is just before you actually display it, the rest of the time just treat it as a normal string and it just works. Of course, on the project schedule you can claim and extra two weeks so that you have time to head to the beach.
Interestingly enough, annoying syntax is one reason why C/C++ tends to be faster.
In python, it's equally easy to do while curr != 'sentinal' versus while curr != 1'. In c, you get annoying doing memcmp or strncmp and quickly go to the numeric based sentinal. This maps to what is *much* easier to do for the computer.
Same with hash tables versus arrays. mydata= {} is as easy as mydata = [] and I have actually seen the former and then the programmer do mydata[0], mydata[1].
And of course there are structs. C really makes you think about organizing your data and doing things that will naturally align things well for using. Versus the much more convenient, but damn near impossible to optimize structures people will build in python.
In fact, sometimes the python syntax makes the harder way easier. For example you want to read part of an array, say 3rd byte and on. In C you might have a pointer and you just do 'b = a + 3'. In python the syntax you would probably gravitate toward is 'b = a[3:]'. This however makes a copy of part of a and points b to the new copy. Python does offer it, but it's a more obscure 'b = buffer(a, 3)'.
XML is like violence. If it doesn't solve the problem, use more.
In most contexts, you have a choice in languages. If I don't like perl, I ignore perl. If I like C, I can write in C. My language choice in general purpose world is free and I can ignore the ones I disagree with.
Javascript in part has a problem because developers that need to do something inside a browser have *no choice*. So people who dislike it and would ignore it cannot get away from it, and so hate it as they work on it.
I personally am not big on Javascript. Two big issues for me:
-The 'standard library' is rather limited, because everyone started bolting on third party code and bundling it and that means it's somehow ok that javascript does not build in some basic functionality (e.g. no good builtin string formatting)
-What functions there are verbose, and I personally don't like camel case, too many trips to the shift key. I have seen too many people go straight to jQuery selectors because it's terse, but it's a dog on performance compared to using those functions correctly...
XML is like violence. If it doesn't solve the problem, use more.
SQL/PSM isn't SQL. It's a second, optional language added to the SQL standards and competes with the likes of TSQL, PL/SQL, and PL/pgSQL. It's an optional extension with different syntax. If you're arguing (by just mentioning it) that SQL/PSM and SQL are the same thing, then we may as well say C#, C++, Objective-C, Cilk, and C-with-classes are all C. Lump Delphi and Ada into the Pascal bucket. Call SML and OCaml both just ML.
Yes, Arduino has a special preprocessor for C++. Many projects have their own preprocessors, template kits, custom configurators, or custom build systems. That doesn't mean the language isn't still C++. Visual C++ is still C++. Delphi is still Object Pascal, and C++ with Boost or the STL or some custom preprocessing that is still written as C++ is C++. The Arduino FAQ lets you know that the recommended language is just C or C++ with some custom functions and some preprocessing. It also goes on to say you can program it in any language that supports the processor so long as you link against the proper libraries. https://www.arduino.cc/en/Main...
What is the ieee?
If you think utf8 is trivial in C, you must not have used it for text containing non-ascii characters, or done only very simple processing. I'm guessing that it's the "only very simple processing" choice, because that is actually not unreasonable.
FWIW I *do* prefer utf8 for file storage, but when a chunk contains non-ascii text I usually transform it into codepoints as that's easier. But it's far easier to just pick a different language. Choices that work are Python, Go, Vala, D, and Racket (i.e. Scheme). I'm sure there are others. Which is best depends on the task in hand. (Note that I didn't mention Java. Java has trouble with unicode punctuation and non-European characters.)
I think we've pushed this "anyone can grow up to be president" thing too far.
Sorry, but no. The annoying syntax is necessary to make the language fast only because of maintaining historical continuity AND remaining a swiss army knife. It's true that the language would have needed to change in other ways to allow the speed without the incredibly ugly syntax. And this basically would have required the language to split into syntactically incompatible subsets, probably, as I guessed earlier, about five.
That said, I will agree that if you are going to make the language maximally compatible with prior versions including keeping the "one tool fits all" form, then maintaining speed requires the (or rather some) horrendously ugly syntax. There were choices, and they didn't make the worst choices. Possibly they were the best choices given the constraints that they accepted.
FWIW, in my opinion the language made a mistake in not splitting in half back around 2000, probably a bit earlier, with one fork adopting (flexibly disable-able) garbage collection, dynamic strings, and possibly a few other things, and the other fork more or less as it went. The tricky thing would be they would need binary compatible compiled code, so you could mix the two languages in the same program. It's hard to say how things would have gone since then, but it would probably have developed several dialects that could be mixed within a compiled program, but not within the same source file.
I think we've pushed this "anyone can grow up to be president" thing too far.
It was trivial because you rarely need to look at the text. Ie, internationalization of constant text that doens't need parsing, only displaying. That is zero text processing. I have seen programs that used wide character support just to handle that case, and they'd convert the multibyte format to wide characters as the first thing to do.
Now if you're doing something like parsing that string, then yes, that's harder. But not necessarily that much harder. If you need specific dellimiters, then strchr will often work. If you're parsing a programming language then lex or strtok will handle this even if you have Asian characters in your comments or strings. That's because no byte within a multi-byte character can be confused with a single byte character (in UTF-8 or most other multibyte formats).
Where it is even harder is if you need to pull apart each character. But there are standard ISO C functions for this that are easy to use.
It usually never gets more difficult than this unless you're doing some types of GUI work.
Generally, when someone complains about lack of Unicode support in C, they usually are talking about wide character support. I'm just pointing out that wide characters are not needed as often as they are actually used.
It was trivial because you rarely need to look at the text. I
You are making invalid assumptions about the kind of processing I was doing. Different tasks demand different tools. I was doing a bit more than just parsing the string. And C's handling of unicode is not satisfactory. (Actually, I also don't like the way it handles, or rather doesn't handle, variable name hiding either, but since I don't really expect the language to protect access I could learn to live with names like: NodeA_instance1_id_prefix. It's hideously ugly, but it can be lived with. Much worse is creating macros to hide the stuff. (I once had to maintain code that someone who liked to do that had written. Never again.) And nests of pointer indirections are a true abomination, that should be hidden by the language. That's stuff that CPU chips like, but which tend to cause untraceable errors when programmers hand craft them.
I think we've pushed this "anyone can grow up to be president" thing too far.
... in Python
"Consensus" in science is _always_ a political construct.
By the time they graduate, all the languages-du-jour will have changed.
The only things that will always be there are assembly, C, C++, javascript*.
* until all the major browsers switch to something else, but they'll never agree to that.
Rust is a new language, not in the list. Sigh...
Leslie Satenstein Montreal Quebec Canada
I am very suspicious of a methodology that puts all of the values so close together and where assembly language even registers... That's like saying a huge portion of development work is being done on MS-DOS!
This seems more like a ranking of which languages people have the most problems with :-)
An engineer who ran for Congress. http://herbrobinson.us