3 ms·
> App Engine hurt them so much they have a hell of a job to recover and now have to compete using someone else's playbook. why did this hurt them? I thought ap
by chii 8y ago
> App Engine hurt them so much they have a hell of a job to recover and now have to compete using someone else's playbook.
why did this hurt them? I thought appengine was great when i used it (granted, i never paid them for it - the free tier was way too generous).
- michaelt 8y agoIt delayed them making the product customers wanted?
- WorldMaker 8y agoIt gave a lot of developers for a long time an impression that Google only really cares about (maybe) Java and Python and other languages are SOL? It gave a lot of developers for a long time an impression that Google both very much wanted proprietary lock-in (App Engine APIs were extremely distinct to other libraries commonly used for those tasks in those languages), but didn't have the dedication to support a lot of backward/forward compatibility and were happy to change those proprietary APIs seemingly on a whim?
- Shakahs 8y agoThree things. First, GAE has drastically, massively improved as a product since it was first introduced in 2008(!). But a lot of people don't know that, and the original reputation remains. Second, App Engine was the original Google Cloud product, it came out years before Compute Engine and never took off like they expected but for awhile it was all they had to offer. Thirdly, in 2011 Google changed the billing model. Datastore requests were no longer free and CPU billing was switched from CPU time to wall time [1]. The old billing model did not account for how some developers were actually using GAE and it was not sustainable, so Google had to make a correction and some apps saw a massive cost increase. This further tarnished the GAE reputation. [1] https://github.com/stickfigure/blog/wiki/The-Unofficial-Google-App-Engine-Price-Change-FAQ https://github.com/stickfigure/blog/wiki/The-Unofficial-Goog...