There are definitely some holes in GAE for Go too, but its not that bad.
Most of the pain points are in other areas. Like for example, the datastore API you have access to for Go doesn't even support geo-spatial data or queries. I had to hack my own solution. It made me pretty mad at the time, because how can you not support geospatial queries in a database in an age where mobile location-based apps are so ubiquitous.
So I can see why you would say the platform is stagnant. And there is probably some truth in what you are saying in terms of GAE not getting the same love as other parts of the Google Cloud.
But having said that, I STILL think there is some merit to building apps on GAE, if your app is a simple web server, or single purpose REST API. I have found that its pretty reliable, and its relatively cheap for what you get.
Comments
There are definitely some holes in GAE for Go too, but its not that bad.
Most of the pain points are in other areas. Like for example, the datastore API you have access to for Go doesn't even support geo-spatial data or queries. I had to hack my own solution. It made me pretty mad at the time, because how can you not support geospatial queries in a database in an age where mobile location-based apps are so ubiquitous.
So I can see why you would say the platform is stagnant. And there is probably some truth in what you are saying in terms of GAE not getting the same love as other parts of the Google Cloud.
But having said that, I STILL think there is some merit to building apps on GAE, if your app is a simple web server, or single purpose REST API. I have found that its pretty reliable, and its relatively cheap for what you get.