4 ms·
The reality is that popularity is hugely important for programming languages. Tooling is important, but you'll only get good tool support if you're popular; the
by lmm 5y ago
The reality is that popularity is hugely important for programming languages. Tooling is important, but you'll only get good tool support if you're popular; there are what, two and a half full IDEs out there, and at least for certain kinds of languages, having first-class support in those IDEs is a much bigger difference maker than anything you can do at an actual language design level. Similarly for things like having big hosted repositories with lots of libraries available, and first-class support in official SDKs.
Don't get me wrong, I wish programming language competition was less zero-sum than it is, but sticking our heads in the sand about it doesn't help.
- mjburgess 5y agoI think this could be a tad outdated. Given generic language tooling innovation (lang server, llvm, ...) it's possible to launch a language with good tooling. Given, also, the ability to piggyback on jvm/.net/cpython-vm (cf. julia)/c ffi/.. its also possible to launch with libraries. I think today language popularity is a lot more about: (1) big name support; (2) killer app/library. If you can't get (1), and you're in the lang. game, i'd be looking at a (2). ie., solve some problem better than its being solved anywhere right now, in your language, in a way which naturally suits it. The opportunity cost (on using poorer solns) then forces adoption.
- lmm 5y agoDisagree; generic tooling is improving but it's a long way from being "there" yet, and FFIs have barely improved over the last 10 or so years; they make it possible to use libraries from other languages, but they don't (and maybe can't) make it idiomatic.
- mjburgess 5y agoI'm thinking of * Piggybacking: Scala/Spark, Typescript/Node, Exlir/OTP, ... * Features: Rust/Saftey, Go/IO, ... * Backers: Go/Google, Kotlin/Google, ... TS/Microsoft, ... You're right that tooling is more important than the intrinsic properties of the language grammer & operational semantics... However I dont think the stories of the above langs have been a story of tooling; in almost every case, quite the reverse.
- lmm 5y agoAs a Scala programmer the tooling was an absolutely vital part of the story. First-class Eclipse support (funded by one particular deep-pocketed company that was using it) was a huge part of Scala's early success, and when Eclipse started losing popularity (in favour of IntelliJ which never really had first-class Scala support, and since started pushing Kotlin) and the plugin stopped being maintained, the language stagnated and hit a slump that it's still not really recovered from. Things like Takipi (now OverOps) were also a huge part of why it was such a good language to work with and a big reason to choose it over the likes of Haskell.
- CaptArmchair 5y agoProgramming languages have a lot in common with natural languages. The viability of the latter tends to be measured by it's native speakers, daily use, proliferation, adoption,... and so on. Linguists and anthropologists don't consider those metrics in isolation though. The evolution of language can only be explained by considering context as well: natural languages are intrinsically tied to communities, tribes, culture, shared identities, shared morals and values, geography and so on and so on. In that regard, this evolution is extremely fluid. Billions of people know more then one language. Languages influence each other, as peoples and cultures meet. Sometimes, languages are adopted, like French was adopted by English elites after the Norman invasion, or Greek was the language of Roman elites. Programming languages share many parallels with natural language. It's a fallacy to assume that programmers are homogeneous group of individuals with no discernible differences. On the contrary, being a programming is just part of one's identity. Most people come to programming because they are interested in solving particular challenges, or contributing to larger goals in specific problem domains or industries. The challenges faced by embedded system engineers in aviation are nowhere near the same as those faced by an frontend engineer specialized in using a particular content management system. Moreover, many programmers don't reduce themselves to a single language. They might know the nooks and crannies of one or two languages in depth - much like a native speaker is innately wired to their mother tongue - but chances are they know a handful languages which are useful throughout their career and daily life, such as they identify parts of it with programming. In that regard, I feel that the 'competition' between programming languages is largely perceived, instead of a real thing. At worst, it leads people into "golden hammer" thinking about the tools they use. The "zero sum" thinking as you've pointed out, then reveals itself for what it is: a self-fulfilling prophecy, self inflicted by tool-centric thinking. And that's exactly what the article is arguing against.
- lmm 5y ago> Programming languages have a lot in common with natural languages. Can you substantiate this claim? They're not used in the same way, their learning patterns are different; the fact that we use the same word is coincidence more than anything IMO. > At worst, it leads people into "golden hammer" thinking about the tools they use. The "zero sum" thinking as you've pointed out, then reveals itself for what it is: a self-fulfilling prophecy, self inflicted by tool-centric thinking. Nonsense. The advantages of having good tooling and ecosystem are very real and concrete. If anything, the idea that particular programming languages are useful in particular problem domains is a lot more of an self-fulfilling prophecy - in my experience any halfway decent general-purpose programming language can be used in every domain if you actually try, usually the only reason to prefer a language with a good reputation in that domain is because there tend to be more libraries and so on, but that itself happens for purely circular reasons. (If you really believe that programming languages are like natural languages, wouldn't you expect programmers to pick one and use it for everything?)
- joelbluminator 5y agoIndeed, when language popularity declines usually the selection of jobs declines; how easy is it for a Perl programmer to get a Perl job? And yes, there is such a thing as a Perl programmer: if the job requires Perl experience they need a Perl programmer, period.