Is this cumulative requests from the past 5 years?
Also what people request and what google's vision is are two different things. Who are they targeting with this PHP stuff. Yes sure, for free-tier stuff, I'm sure lots of kids playing around with PHP would love to have a sand-box to play around. But this move seems inconsistent with their prior action that signaled a move toward enterprise sales.
Also, it feels like one side of google is not talking with the other side. They're building a whole application scripting system hosted on google Drive to work with google apps, etc. Why not provide the javascript on GAE to allow further application development and integration.
To be honest, this feels like: Oh shit! Google I/O is coming up and we need to have something to show than a vision of providing cloud-based computing solution that fits within their big vision.
> Also what people request and what google's vision is are two different things.
Google's vision is "developers deploying scalable apps on App Engine". Being developer-friendly is good for that.
> Who are they targeting with this PHP stuff.
Existing PHP devs. Which is a lot of devs.
> Yes sure, for free-tier stuff, I'm sure lots of kids playing around with PHP would love to have a sand-box to play around.
Lots of apps that end up making money use PHP.
> But this move seems inconsistent with their prior action that signaled a move toward enterprise sales.
Enterprise is an area that Google would like to get their Cloud Platform, including App Engine, more sales in, but its never been anywhere close to their sole target for it.
> They're building a whole application scripting system hosted on google Drive to work with google apps, etc.
"Building"? Apps Script has been around a long time (longer than Drive itself; maybe longer than App Engine.)
> Why not provide the javascript on GAE to allow further application development and integration.
Javascript on GAE would make a lot of sense, too (especially in light of App Script and Google's work on V8 and the emerging popularity of Node.) So would Dart-on-GAE. I wouldn't be surprised if either (or both) of those happened. But the fact that it makes sense doesn't make PHP make any less sense.
> To be honest, this feels like: Oh shit! Google I/O is coming up and we need to have something to show
App Engine PHP wasn't even the big Cloud Platform announcement tied to I/O; general availability of the Compute Engine IaaS (and the associated new pricing and instance types for Clound Engine) was the big Cloud Platform news.
> than a vision of providing cloud-based computing solution that fits within their big vision.
Google's big vision for cloud-based computing is, well, big. It includes more than one kind of solution, for more than one market segment.
"Lots of kids playing around with PHP"
"People who want to play around with "hello worlds" with PHP"
Your attitude is ridiculously arrogant.
PHP powers most non-corporate website on the web. The wast majority of wikis, blogs and forums. You know, things that are used for actual communication and knowledge sharing by millions of people.
Google Drive / apps script integration is a great idea. Unifying our storage offerings across the entire company is a great idea too (but an aside for this conversation). I disagree with the "get something out" mentality, though. Shipping a fully managed runtime that scales as well as Java, Python, and Go, that is hardened, and is secure enough that we'll run it next to Gmail, Search, Geo, etc. is no easy task. It's not something you decide to do on a whim a few weeks before i/o.
Also what people request and what google's vision is are two different things. Who are they targeting with this PHP stuff. Yes sure, for free-tier stuff, I'm sure lots of kids playing around with PHP would love to have a sand-box to play around. But this move seems inconsistent with their prior action that signaled a move toward enterprise sales.
Also, it feels like one side of google is not talking with the other side. They're building a whole application scripting system hosted on google Drive to work with google apps, etc. Why not provide the javascript on GAE to allow further application development and integration.
To be honest, this feels like: Oh shit! Google I/O is coming up and we need to have something to show than a vision of providing cloud-based computing solution that fits within their big vision.