Google to announce new App Engine runtime for "very popular language" at I/O
plus.google.com
plus.google.com
Do it in 30 seconds:
mkdir ~/testypoo && cd ~/testypoo
echo "<?php phpinfo(); ?>" > index.php
git init
git add .
git commit -m "woohoo php in the cloud!"
heroku create
git push heroku master
"Simple" and "free", sure, but "enjoy"?
So yes. I enjoy using PHP for all its faults.
However, "productive" and "latest frameworks/languages" is a bit of a false dichotomy.
As for cheap shots at PHP, I see PHP like the USA. Easy to take cheap shots at because its so large and runs so much. For all its faults/flaws its still pretty productive though.
I am an Aussie for the record.
I've never seen that. I've seen many programmers claim that they will be more productive in new language/framework X because it includes a combination of features A, B, and C that aren't found together in other languages/framewors, but never simply because the language/framework is new.
The closest I've seen to the "because its new" thing is "because it doesn't have the accumulated cruft of framework Z", but while that may be related to newness, its still about features, rather than newness alone.
Don't get me wrong, i'm all for new technology but bleeding edge on new projects can be a recipe for failure most of the time.
That's a fairly good reason for bleeding edge to be used as one track of a dual- (or multi-) track project which includes a short-turn-around, low-risk, low-reward track and one (or more) higher-risk, high-reward, longer-turnaround track.
This is equally true regardless of whether the project is "new".
I then asked if I can use the platform for non-Facebook apps. Here's their response:
"Hi– it's not yet officially supported, but if you try pushing one, you'll find that it works."
To use:
heroku config:add BUILDPACK_URL=git://github.com/iphoting/heroku-buildpack-php-tyler.githttps://groups.google.com/forum/?fromgroups=#!topic/google-a...
Headline roughly translates to "we're willing to pay the perpetual maintenance cost of a new runtime because our existing runtimes aren't attracting enough users to justify the product", and the reasons for that cannot be fixed by adding yet another layer of lipstick to a pig.
Having worked on 7k+ reqs/sec sites on App Engine I can expand on this in great depth, but please google my comment history before making me write another essay!
So that doesn't even make sense as explanation.
I doubt that desperation is an issue.
> Headline roughly translates to "we're willing to pay the perpetual maintenance cost of a new runtime because our existing runtimes aren't attracting enough users to justify the product"
No, it doesn't. You may interpret it that way, but that's not a translation, that's your unsupported ascription of a motive.
It would be at least as justifiable an interpretation to say that this is a sign that the AppEngine platform has matured as a standalone product (rather than just a way to derive some incidental revenue at low cost from infrastructure Google has to have to support their core services) that they are getting around to supporting languages with heavy market demand but little internal traction in Google, rather than what is internally-useful to Google.
A WordPress port might also make a strong full service option for SMB's self-hosting their public corporate site on Word Press but using Google Apps for email and corporate infrastructure. Now they can put it all on the same P/IaaS.
Can you imagine how awesome it would be if they actually supported this on GAE?
Can't say PHP is my favorite but I know lots people who use it every day.
Will it take 5 years before they have ruby on rails?
I assume/hope that it's not so much that people want to use PHP on AppEngine as it is they want to use popular PHP applications (WordPress and so on).
Dart doesn't come close to qualifying as a "popular" language.
Fixed. :)
I can see why PHP makes sense, though, even though I have zero interest.