News for hackers. Stuff that matters.

A comment on The Python Paradox Is Now the Scala Paradox (2009). Parent comment

Re:The Python Paradox Is Now the Scala Paradox (2009) by TheMagicHorsey on Saturday September 17, 2016 @12:08PM (#12521053)
You may be right. I work in the Bay Area, and I see a lot of devops projects in Go these days. In fact, I'm hard pressed to find a new devops project that isn't in Go.

But I agree that the Bay Area, and San Francisco specifically, is a bit of a bubble. So its very possible that there is little Go traction in other cities.

[ Parent | on HN ]
Re:The Python Paradox Is Now the Scala Paradox (2009) by XorNot on Saturday September 17, 2016 @12:30PM (#12521153)
Go has devops traction because of it's deployment story. It solves a bunch of problems people have with trying to use Python for the types of things you do in devops.
[ Parent | on HN ]
Re:The Python Paradox Is Now the Scala Paradox (2009) by BerislavLopac on Saturday September 17, 2016 @04:28PM (#12522293)
Such as? I'm honestly interested what problems you have in mind, not implying that they don't exit.
[ Parent | on HN ]
Re:The Python Paradox Is Now the Scala Paradox (2009) by bogomipz on Sunday September 18, 2016 @12:42PM (#12525946)
Distributing artifacts for one, a single self-contained binary in the case of Go vs a virtualenv or buildout for shipping and managing dependencies for a Python app.
[ Parent | on HN ]