Re:Why Google App Engine Rocks: A Google Engineer’s Take
by NearAP on Friday May 06, 2016 @05:23PM
(#11646809)
I believe I've made this comment before - Google App Engine is good and quickly allows you to get a proof of concept off the ground. But the documentation SUCKs big time - the language is obtuse, the documentation is repeated in multiple places (meaning different paths to documentation explaining the same thing in different ways), and it is not uncommon to find that the documentation is not current.
[ Parent
| on HN ]
Re:Why Google App Engine Rocks: A Google Engineer’s Take
by pseudobry on Friday May 06, 2016 @05:28PM
(#11646833)
You should take another look, as we literally rewrote most of the documentation in the last few weeks.
Re:Why Google App Engine Rocks: A Google Engineer’s Take
by rstupek on Friday May 06, 2016 @11:31PM
(#11648267)
The google cloud documentation is definitely sub-par. I tried to build a simple Go app trying to use the pubsub api and eventually gave up. None of the documentation provided a full working example and any example you can find references an old version of the api. And this was with Go!
Re:Why Google App Engine Rocks: A Google Engineer’s Take
by alttab on Friday May 06, 2016 @05:47PM
(#11646934)
What's missing from this fluff piece is the top 5 reasons why its better than AWS.
Re:Why Google App Engine Rocks: A Google Engineer’s Take
by dragonwriter on Friday May 06, 2016 @06:03PM
(#11647018)
> What's missing from this fluff piece is the top 5 reasons why its better than AWS.
AWS and AppEngine aren't even the same kind of thing. AWS is a high-level collection of services (Google's equivalent is Google Cloud Platform.)
AppEngine is a PaaS offering within Google Cloud Platform. And, AFAIK, its one piece of GCP that AWS doesn't have a direct competitor to. (Lambda is, I think, the closest thing.)