News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by oblio on Wednesday October 18, 2017 @03:56AM (#15497582)
I'd say that simplest "production-ready" criterion is this: does it have an officially supported and stable release of a IntelliJ IDE (there is a slight Java-ecosystem bias, but I think it's only slight).

So the mainstream languages are...: C/C++, C#, F#, Go, Groovy, Java, JavaScript, TypeScript, Kotlin, Objective-C, PHP, Python, Ruby, Scala, SQL, Swift, VB.NET (source: https://www.jetbrains.com/products.html).

Sounds about right :)

Re:Why we switched from Python to Go by majewsky on Wednesday October 18, 2017 @09:25AM (#15498913)
So, from the top of my head, Erlang, Haskell, OCaml, Perl, Fortran, Cobol and any type of shell script is not production-ready. Nice to have that clarified. :P
Re:Why we switched from Python to Go by sjellis on Thursday October 19, 2017 @02:06AM (#15505775)
It was a very bad choice of words.

I wish that I knew a phrase to mean "has all of the documentation, tools, and libraries that are needed for an average team of developers following common practices to be likely to successfully ship and effectively maintain commercial projects, consistently".

Many really interesting languages and frameworks don't pass this criteria. It doesn't mean that they are a failure: the idea of programming languages that are designed for teaching or research, and are specifically not for commercial use, perhaps used to be more common than it is now.

Re:Why we switched from Python to Go by oblio on Thursday October 19, 2017 @09:06AM (#15507501)
Your 100-ish character phrase is probably the most succinct description of an idea I've frequently wanted to express.
Re:Why we switched from Python to Go by gbersac on Wednesday October 18, 2017 @09:36AM (#15498983)
They may be production ready, but have a quite small ecosystem compared to other languages mentioned.
Re:Why we switched from Python to Go by saghm on Wednesday October 18, 2017 @02:56PM (#15501901)
Do shell and Perl really have a "small ecosystem" compared to something like Groovy?
Re:Why we switched from Python to Go by oblio on Wednesday October 18, 2017 @09:40AM (#15499022)
Or there's not that many greenfield projects in any of them, for those that have managed to acquire the ecosystem years ago.
Re:Why we switched from Python to Go by weberc2 on Wednesday October 18, 2017 @10:11AM (#15499273)
I'm the opposite; I don't stick much time into learning a language if it doesn't have a high quality vim plug-in and command line tooling. It's fairly shallow, but I want to learn how things work behind the scenes, and I don't like fighting the editor over my preferences. It's a lot of small things, but why not enjoy your hobby time? This is just my personal preference and I understand and respect that there are lots of folks who enjoy their IDEs like I enjoy vim/Unix.
Re:Why we switched from Python to Go by vorg on Wednesday October 18, 2017 @02:56PM (#15501899)
> So the mainstream languages are...: C/C++, C#, F#, Go, Groovy, Java, JavaScript, TypeScript, Kotlin, Objective-C, PHP, Python, Ruby, Scala, SQL, Swift, VB.NET

Of those 18 languages, only 13 are in the TIOBE top 50. Two of them (Apache Groovy and TypeScript) don't appear in the TIOBE top 50 so it's pushing credibility to call them "mainstream" languages -- the Java-ecosystem bias is more than "only slight".

Re:Why we switched from Python to Go by saghm on Wednesday October 18, 2017 @02:56PM (#15501897)
Slight nit, but I don't think it's accurate to say that Go has an "officially supported and stable release of an Intellij IDE". While Gogland is excellent (I use it as my main Go editor at work), I think it's still technically in pre-release.

On a more unrelated note, is Groovy widely used? As someone who doesn't really ever use JVM languages, my impression was that it didn't have the similar usage to Kotlin and Scala, although I might be mistaken.

Re:Why we switched from Python to Go by vorg on Wednesday October 18, 2017 @03:06PM (#15501980)
Apache Groovy's used for scripting on the JVM, like Bash and Perl on Linux. It's OK for glue code, mock testing, and 10-line build scripts in Gradle. But 5 years ago, some of Groovy's backers tried to re-purpose it as a competitor to statically typed languages like Java, Kotlin, and Scala, which is when things went awry. If it had stuck to its knitting, it could have been used widely for scripting classes written in Kotlin and Scala as well as Java. But it didn't even keep up with Java -- it doesn't even have Java 8's lambdas on the eve of Java 9's release.