5 ms·
It seems to me that the evidence is that in the 2010s, it is exceedingly difficult for a new language to break into what I call the "B-class language list" (the
by jerf 11y ago
It seems to me that the evidence is that in the 2010s, it is exceedingly difficult for a new language to break into what I call the "B-class language list" (they aren't in the Nobody Was Ever Fired For Choosing (Java/C#) set, but the languages you can use pretty much anywhere but Big Enterprise without anybody raising an eyebrow, like Python or Ruby) with some sort of serious corporate backing.
There hasn't even been much from the 200xs that has broken into that list. Looking at the Tiobe list for concreteness (yes, it may not be perfect but it isn't completely wrong, either, so close enough), you have to go to 14 to Swift to find something not from the 20th century. At 17 (Groovy) you debateably have something that wasn't pushed by a company (that's actually a complicated question), and all the way down to 21 to get to D to find the first thing that clearly comes from a single person anytime recently. (I won't go any farther because the list probably is getting to be just noise below that.)
I hypothesize that it is because we expect so much from our languages now. If you don't have a solution for serving web pages from your new language, don't even hope to make that list. But it could also be because developers are nervous about choosing something so obscure and having it just fade away when the competition that doesn't have that problem is already pretty good. Compared to 20 years ago we are spoiled for choice, so perhaps getting your head about the rest even in a niche is simply harder than it used to be. But I really don't know what it is.... but observationally, it seems to take a lot more than just "being a good language" nowadays to attain great success in the computer language area.
PS: This is the sort of thing that leads me to disagree strongly with the idea that the computer world moves quickly. When it requires more than half an average career for dominant language to shift, that's not "fast".
- NhanH 11y agoClojure and Scala? I know they are backed by companies, but those companies were founded to support them (ie. the companis grew with the language). Elixir would be joining the B-class language really soon.
- jerf 11y agoNot in my B-list, no. Clojure and Scala are still going to get the "Never heard of it" from a lot of developers, and right now the developer who has heard of Elixir would be the exception, let alone being able to say "I wrote that in Elixir" to your boss with no eyebrow raises. YMMV depending on your boss, of course, but I think that's a fair characterization of the "average boss". I don't even put Go in list with Google's corporate support, since it still certainly produces eyebrow raises. The B list mostly consists of the 1990s-style dynamic scripting languages right now; Python, Ruby, PHP, etc. There's a lot of up-and-coming alternatives but nothing leaps to mind that won't likely need to be defended. There is, of course, no concrete definition of the B-list, so you are free to have your own; rather than arguing with me too much about what language falls where, if you want to propose a different definition for conversation, please do. It's a fun discussion, if ultimately pointless. I'd put what you mentioned in a separate C list, "the set of languages that are known about on HN and have been used for real projects but still generally need defending if you want to choose them". It's a much longer list. All the fun languages are on it. Erlang's still a C-list in my book, so first Elixir will have to pass Erlang before I'd even consider it in the B list.
- flatline 11y agoAgreed. The problem with Clojure and Scala is that they naturally target Java developers, due to their dependence on the JVM and tight integration with existing Java libraries. Companies choose Java for, among other things, the relatively simple syntax and ubiquity of Java developers. This is not a group that is, as a group, longing for change, for something new and more expressive. Java's selling points are static typing, corporate backing, large-scale adoption, memory safety, verboseness, and write-once-run-anywhere. Clojure gets rid of static typing and you can easily write completely opaque, unreadable code in Scala[0]. They are DOA in most large organizations off the bat for these reasons. And for someone looking for native compilation or predictable memory management, they are also off the table. [0] http://blog.fogus.me/2009/03/26/baysick-a-scala-dsl-implementing-basic/ http://blog.fogus.me/2009/03/26/baysick-a-scala-dsl-implemen...
- the_af 11y agoReally? Your example of "unreadable" Scala code is a DSL specifically designed to look like BASIC, complete with line numbers? Have you taken a look at the source code? It's extremely simple, short and easy to understand. It even says so in the blog post you linked to. The only way I can figure someone not understanding it is if they think "these don't look like Java keywords, I give up!". Also, I don't know about Clojure, but Scala isn't DOA in large organizations.
- flatline 11y agoMy point being, Scala is a powerful and expressive language in which you can write something like a basic DSL. I personally think this is great, but a lot of Java secs will take one look at that level of flexibility and faint when trying to imagine a group of 10 developers of wildly varying ability and experience trying to manage a large code base with a language like this. Really, I've tried to introduce Scala in Java teams before, and was surprised at the pushback over just the concept of a different language running on the JVM. Groovy is apparently an exception, but I have not seen it used as the primary language over Java.
- chubot 11y agoI think language adoption follows broader trends in the industry. In the early 90's, people were coding for desktops, so you could use C, C++, Pascal/Delphi, or Visual Basic. You had a lot of closed source languages. The web brought us Perl, PHP, Python, Ruby, and JavaScript, which are all pretty darn similar if you squint. Java is sort of an outlier because it was commercial and free and had a lot of marketing. Mobile phones lead to a resurgence in Objective C, and another big market for Java. Since we're still making websites, we're still using the same languages for them. Languages naturally have a network effect that is hard to break. If you already have N modules, writing the N+1 module in the same language is the path of least resistance. And then module N+1 also makes the ecosystem more valuable. C++ has an especially pernicious network effect, because it's so difficult to interface with it (in general). If languages were more interoperable, then this network effect could be broken. But in practice it seems the main way to break the network effect is for a new generation of technology to come around. ALL languages are really domain-specific. And it is fantastically expensive to build a language ecosystem... so as long as the domain remains the same, the language will likely remain the same. I think the hardest thing to break is going to be our foundations in C/C++. Mainly because every single other language is also written in C/C++ (Perl/PHP/Python/Ruby/JavaScript/Java). An earlier special case of this is that it's easier to write an application in the same language that the operating system is written in, or a language written in that language -- which is of course always C or C++. The OS specifies its portable interface in C headers, and in C data types. Possibly domains that will create new languages: AI, big data, distributed systems (Most things are built on top of existing languages, like Spark on Scala, Flume on Java, TensorFlow on Python, but there might be room for a first class language once we figure out what the heck we're doing!)
- nostrademons 11y agoLanguage adoption is pushed by platforms. New languages get adopted when there's a new platform that people wish to develop for, and existing languages aren't suitable for it. That's behind Swift's rapid rise (it's being pushed as the "new official" language for iOS) and a lot of historically successful languages. BASIC was the language of the early microcomputer era. C was the language of the UNIX & Win32 era. PHP and Perl were languages of the Web 1.0 era, and Javascript, Ruby, and Python of the Web 2.0 era. Objective-C is for Mac and iOS development, and Swift is soon to replace it. C# is for .NET development. Java was pushed as the language for the web, but ultimately found adoption within the enterprise, and I think Go is headed toward a similar position. The reason we've seen all the major languages of the past 10 years backed by large corporations is because all the major platforms are controlled by large corporations. The web was the last totally-open computing platform to see widespread adoption, and there was a large renaissance of single-developer programming languages for it. We've been in a similar position in the late 80s and early 90s, when C was completely dominant along with Windows & commercial UNIXes, and it turned out that pattern reversed itself in a few short years.
- zzzcpan 11y agoI don't think the platform thing is that big of a deal. Programming languages are pushed and promoted just like everything else in the world. But there are more programmers than ever before, more languages than ever before, more platforms, more everything. And reaching out to most of the programmers becomes much harder and convincing them to use a new shiny language even more so. If anything, we are likely to never see any new language become mainstream again. And likely to see most of the mainstream languages fade away.
- dilap 11y agoi don't buy it. orgs coding in java or go or python or ruby on the backend can be coding in anything; it's not being pushed by a platform. bazqux, the only good rss reader after the greader diaspora, is freakin' ur/web. swift, while apple is trying mightily to support it like a first-class citizen, is really more like an adopted child, platform support wise. it's interesting because of the language, not the platform.
- 11y ago
- vorg 11y ago> Looking at the Tiobe list for concreteness [...] At 17 (Groovy) No need to consider whether Groovy follows the trend or not. Tiobe gives a history of all Top 20 languages as a graph, just click on the language name in the top 20 chart. Groovy's ( http://www.tiobe.com/index.php/paperinfo/tpci/Groovy.html http://www.tiobe.com/index.php/paperinfo/tpci/Groovy.html ) shows the most volatile movement in the rankings (e.g. it just rose from #82 to #17 in a mere 12 months), and Tiobe's comment "Scala might gain a permanent top 20 position soon" is probably a back-handed dig at the likely impermanence of Groovy's top 20 position. That language is being actively fiddled through the popularity rankings.