[throwaway_374]

As an aside, the greatest thing about Python is StackOverflow one-liner solutions to common problems. How do you find your developer productivity fares in Go? To take a simple example, I was experimenting with C++ and had the simple task of "reading in a CSV". This simple C++ task does not have a nicely formatted, pre-approved, community rubber-stamped, best practice 500 green ticks StackOverflow top accepted answer (sometimes by Core Python / prominent PyCon developers) that I can just copy and paste.

[bpizzi]

> How do you find your developer productivity fares in Go? To take a simple example, I was experimenting with C++ and had the simple task of "reading in a CSV".

Not sure if reading data from a csv formatted file is a great example for differentiating Python and Go: both languages have a builtin csv package/module.

Python: https://docs.python.org/3/library/csv.html#examples

Golang: https://golang.org/pkg/encoding/csv/#example_Reader

And, errors handling put aside, both takes more or less the same number of LOC.

[tonyedgecombe]

> And, errors handling put aside, both takes more or less the same number of LOC.

So apart from the difference in line count they are the same line count :)

[slrz]

Right, it's almost impossible to get any work done without having pre-approved code to copy and paste from. This is especially true for highly complex problems like reading a CSV file. Those virtually require the presence of promiment PyCon developers as no one else can possibly get this right.

Only use code with at least 500 green ticks.

[throwaway_374]

I always appreciate a healthy dose of sarcasm, but I think you're missing the wider point about the great community we have in Python - not only in terms of the ecosystem, but also continuous guidance on best practice for common problems.