Comment Re:they should just create GLang (Score 1) 247
then raise prices significantly.
That's debatable. The pricing model changed, and it's likely more expensive, but also clearer and potentially cheaper.
Oh, and since it's unique platform and the backend is closed, you either have to accept whatever price Google is asking or abandon the project and code it again from the beginning.
Disclaimer: I contribute to dm-appengine, a DataMapper (for Ruby) layer for Google App Engine. It's part of why people can run Ruby on Rails on JRuby on App Engine.
But I think dm-appengine alone makes a compelling case that you don't have to code from the beginning unless you've done something fantastically stupid. DataMapper has backends in everything from sqlite to Oracle, from RDF to IMAP. It's entirely possible to develop an app which targets both MySQL and App Engine. You'll probably have some porting work, but it's hardly a "code everything from the beginning" situation.
If you developed for Python or Java, there's appscale, and I'm not sure that's the only alternative. You could port your entire app as-is from App Engine to Amazon EC2, or to your own private Eucalyptus infrastructure.
Also, note that Google has made no aggressive moves against these organizations. I don't just mean lawsuits; they haven't even been passively-aggressively mentioning "We might maybe sort of have some patents on that App Engine stuff."
You might have a point here:
So much for Google's openness.
But Google never was completely open source all the time. I can't download the source to Google Docs -- or, for that matter, Google Search -- and launch my own competing service. I have a much bigger problem with lock-in, but it looks like they aren't doing that here.