News for hackers. Stuff that matters.
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.