News for hackers. Stuff that matters.
Re:Leaving Go by bsg75 on Monday April 28, 2014 @02:28PM (#7661931)
When X is Python, and "time X" is too slow.
Re:Leaving Go by tptacek on Monday April 28, 2014 @02:30PM (#7661949)
Or "likelihood that program runs correctly if compiles correctly X" is too low, or "ability to write concurrent code in straight-line fashion rather than with callbacks X" is "too low".
Re:Leaving Go by bsg75 on Monday April 28, 2014 @02:38PM (#7661990)
Not sure I follow.

When single threaded top-down Python is too slow for a particular task, of late I find it easier/cleaner/faster to use Go routines than multiprocessing / threading in Python, because of the way concurrency was designed in Go, but added to Python.

> "ability to write concurrent code in straight-line fashion rather than with callbacks X"

Same concept or different point?