Golang has libraries for all of the things you mentioned, and web tools to generate APIs based on those schemas. There's no advantage here over Go.
> And maybe the dependency injection system.
Go has interfaces, which facilitates easy DI. No advantage there, and Go sells itself on not having a magic DI framework like the crap Angular 1 had.
> And Python's ecosystem with lots of packages.
Python's ecosystem may have more packages taken as a whole, but Go has a richer web and infrastructure community thanks to being a web first language and growing out of the DevOps community.
> And that Python is the best/main way to do Machine Learning/Deep Learning.
Which means nothing. You shouldn't be running ML in your web server. You use grpc or http to make requests to your ML backend, or generate a config for the web server to consume.
> I personally don't think new asyncio (Python 3.6) is more difficult, but that's more personal taste.
Even if it isn't more difficult, functions have to be colored async which leads to ecosystem fragmentation. It's a huge pita.
Have you considered that maybe not every one wants have anything to do with the 8th wonder of the world that is Go?
Take it easy pal, let people enjoy things.
Would you cite some? I would love to see the links, packages, etc. And how could you achieve the same in Go:
Having a single type declaration, get web data validation, serialization, documentation with OpenAPI and automatic clear error responses.
I would love to see it, because before building FastAPI I looked for it in Go-land a lot too, and didn't find it, not even closer to the tools that already existed in Python.
And maybe the dependency injection system.
And Python's ecosystem with lots of packages.
And that Python is the best/main way to do Machine Learning/Deep Learning.
I personally don't think new asyncio (Python 3.6) is more difficult, but that's more personal taste.
Indeed, FastAPI inherited benefits from ideas in Go and other languages and frameworks.