News for hackers. Stuff that matters.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by untog on Friday May 06, 2016 @05:20PM (#11646787)
> (Too many AWS "devops" people protecting their jobs?)

I don't think so. A good while ago GAE was incredibly limiting - it certainly was when I tried it. Python only (maybe also PHP?), forced to use Google Cloud whatever for storage, etc. By comparison, AWS was using MySQL databases and EC2 boxes that let you use whatever language you wanted.

I know things have come a long way since then, but the reputation persists.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by bradleybuda on Friday May 06, 2016 @05:24PM (#11646811)
Agreed; GAE's initial feature set was not great, and I think some of that launch stink unfortunately still sticks. As a counterpoint, you see lots and lots of love on HN for Heroku, which is a PaaS in much the same vein as GAE.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by cbsmith on Friday May 06, 2016 @06:02PM (#11647013)
GAE vs. EC2 is kind of the wrong comparison though... GAE is kind of more like AWS Lambda, or maybe bit like ECS or Elastic Beanstalk (and even then not really).
Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @05:40PM (#11646894)
> Python only (maybe also PHP?)

They now support Python, PHP, Java, Go.

And in beta, "flexible environment", which is like elastic beanstalk but more sensible: Python, Java, Go, Node.js, Ruby, <random docker images>.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by democracy on Friday May 06, 2016 @05:59PM (#11646991)
While they are java keywords as we know them this is not a complete jdk, so many (almost single good one) libraries dont work. I remember spending a week trying to port itext pdf generation lib to gae. While it worked we got concerned by the legal issues of us riping code out of sun/ibm/harmony jdks to add missing jdk classes.

Java here is a pure marketing effort to convince a clueless manager saying hey we got java!

Re:Why Google App Engine Rocks: A Google Engineer’s Take by edwinnathaniel on Friday May 06, 2016 @06:36PM (#11647203)
> Java here is a pure marketing effort to convince a clueless manager saying hey we got java!

What if there exist Java-based system that somehow can be deployed to GAE with minimum changes...? (e.g.: not needing itext)

What if there exist a company that the majority of developers prefer Java?

Re:Why Google App Engine Rocks: A Google Engineer’s Take by dragonwriter on Friday May 06, 2016 @05:37PM (#11646884)
> Python only (maybe also PHP?),

I think the order in which GAE added languages was Python, Java, Go, PHP.

Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @05:31PM (#11646847)
It's not protectionism; it's ignorance? ;)
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.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by untog on Friday May 06, 2016 @05:54PM (#11646971)
Reputations are hard to shake. When it launched GAE was one big vendor-lockin, and we all avoided it.
Re:Why Google App Engine Rocks: A Google Engineer’s Take by johansch on Friday May 06, 2016 @06:14PM (#11647075)
When GAE launched I found it to be a cool toy, played with it a little and dismissed it - way too much lock-in.

After revisiting it the past year.. I don't really understand why the in comparison pathetic AWS Lambda gets so much more attention, for instance.