On: Leaving Go

[kermatt]

If you are looking for X, Y will disappoint you.

-or-

If you are looking for X, use X.

[pekk → kermatt]

Unless X is Python, then use Go (??)

[kermatt → pekk]

When X is Python, and "time X" is too slow.

[tptacek → kermatt]

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".

[kermatt → tptacek]

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?