News for hackers. Stuff that matters.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by toomuchtodo on Friday May 06, 2016 @05:47PM (#11646926)
Ignorance about getting locked into an ecosystem its harder to get out of? Hardly.

But heh! You do you, I'll keep my platform agnostic config management thank you very much. Life's too short to be beholden to any one vendor.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @05:49PM (#11646948)
There is really no lockin at all if you use e.g. Flask via the WSGI interface. That is the beauty of it.

You can downgrade to manally managed servers with the the same codebase.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by toomuchtodo on Friday May 06, 2016 @05:50PM (#11646952)
> You can downgrade to manally managed servers with the the same codebase.

Or you spend the few extra hours upfront wrapping your app in config management so it can run on any bare VM.

Don't be lazy! Not being able to run anywhere is technical debt. Unless you're running a hobby site that generates no revenue; in that case, do whatever.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @05:57PM (#11646983)
YAGNI. Do it when you know that you need it.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by MichaelBurge on Friday May 06, 2016 @06:17PM (#11647092)
YAGNI does not apply to risk mitigation.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @06:25PM (#11647153)
I think Google would let us know in advance if they ever decided to retire AppEngine.