# Why the author chose not to switch from Python to Go

DevFeed: [Why the author chose not to switch from Python to Go](<https://devfeed.tech/articles/why-not-go-golang-there-32200.md>)

Original publisher: [Read original article](<https://bruceeckel.com/2015/02/15/why-not-go-there/>)

Author: Bruce Eckel

Published: 2015-02-15T00:00:00Z

Content type: opinion

Language: en

Sources: [Bruce Eckel - Computing Thoughts](<https://devfeed.tech/sources/bruce-eckel-computing-thoughts.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [C++](<https://devfeed.tech/topics/c-plus-plus.md>), [Python](<https://devfeed.tech/topics/python.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>)

Tags: [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [generics](<https://devfeed.tech/tags/generics.md>), [go](<https://devfeed.tech/tags/go.md>), [golang](<https://devfeed.tech/tags/golang.md>), [python](<https://devfeed.tech/tags/python.md>)

## AI overview

The author discusses Go's built-in build tool, formatting, testing, and concurrency support, but explains that these strengths were not enough to prompt a switch from Python. The article also considers Go's relationship to C++ and identifies generics as a significant gap.

## Source excerpt

While there are a LOT of things I really like about the Go language, the bottom line is that I don't use it (mostly because when I studied it the libraries were kind of scarce, something that's apparently changed a lot). It attracted me, but not enough for me to change over from Python. Go has made some brilliant design decisions. I especially like the built-in features that in most other languages you must go figure out for yourself -- like the build tool, standard formatting (enforced with go fmt) a test framework (which you run with go test), and natively-supported concurrency/parallelism.