I can see Go slowly eating Python's lunch for web services here. It's close to Python's productivity and much less resource-hungry while being more performant for many use cases.
Go still has a way to go in terms of productivity-boosting frameworks in comparison to Python though. I hate the tight coupling of and patterns of Django but if I had to spin up a company in a month, there's no doubt I would do it Django.
Lots of people will say "frameworks are an anti-pattern in Go" and I generally agree with the sentiment of writing boilerplate to stitch together various libraries > giving control to the framework.
Still, some people want big hefty, quick-to-production frameworks with everything & the kitchen sink built in. I'm certain we will see those come into existence for Go.
Go still has a way to go in terms of productivity-boosting frameworks in comparison to Python though. I hate the tight coupling of and patterns of Django but if I had to spin up a company in a month, there's no doubt I would do it Django.
Lots of people will say "frameworks are an anti-pattern in Go" and I generally agree with the sentiment of writing boilerplate to stitch together various libraries > giving control to the framework.
Still, some people want big hefty, quick-to-production frameworks with everything & the kitchen sink built in. I'm certain we will see those come into existence for Go.