News for hackers. Stuff that matters.
Re:From Python to Go: migrating our entire API by mikesf888 on Thursday September 10, 2015 @12:08PM (#10198854)
my favorite quote: "Writing software in languages like Python or Ruby often seduces you into being ignorant of what’s going on under the hood because it’s just so easy to do pretty complex things, but languages like Go and C don’t hide that."
Re:From Python to Go: migrating our entire API by erokar on Thursday September 10, 2015 @12:33PM (#10199036)
Damning with faint praise. Often, you don't need to know what's going on under the hood, and often it's not very interesting.
Re:From Python to Go: migrating our entire API by marcosdumay on Thursday September 10, 2015 @01:22PM (#10199332)
To tell the truth, Python is an easy target here, but I doubt 99.9% of the projects in C or C++ care to manage memory as closely as GHC does under the hood. (The same way as they don't manage concurrency.)

Some times, it's even better not to look.

Re:From Python to Go: migrating our entire API by bjt on Thursday September 10, 2015 @02:00PM (#10199531)
I read that but I can't see what he's getting at. Go is garbage-collected just like Ruby and Python, right?
Re:From Python to Go: migrating our entire API by azth on Thursday September 10, 2015 @03:31PM (#10200045)
The original comment didn't make a lot of sense. Go still has many things going on beneath the scenes, including GC and interfaces.