5 ms·
Google to announce new App Engine runtime for "very popular language" at I/O
- sylvinus 13y agoI hope people will put some effort in making WordPress compatible with App Engine. WordPress' reliance on local files is usually a big pain point.
- SkyMarshal 13y agoThere also seems to be a dearth of good FOSS CMS's for AppEngine, which would otherwise be a great platform for that. 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.
- jamesjguthrie 13y agoSweet, been wanting PHP support on App Engine for a long time.
- jeffgreco 13y agoThe pre-release of the python SDK released yesterday contains a PHP runtime https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/0M3fYkN8y0c https://groups.google.com/forum/?fromgroups=#!topic/google-a...
- manacit 13y agoI was hoping for node or dart, but it looks like PHP instead?
- codeka 13y agoPHP is the #1 feature request on their tracking page (and has been since almost day 1). 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).
- frostmatthew 13y agoDart doesn't come close to qualifying as a "very popular" language.
- tnuc 13y ago>Dart doesn't come close to qualifying as a "very popular" language. Dart doesn't come close to qualifying as a "popular" language. Fixed. :)
- dragonwriter 13y agoIn the moments between the time I saw this and the time I saw that it was almost certainly PHP, I was hoping for JavaScript, with Ruby as a close second preference. I can see why PHP makes sense, though, even though I have zero interest.
- michaelwww 13y agoI really doubt it's Dart, which is not ready for this kind of service.
- ChuckMcM 13y agoLet me guess, "Go" ? :-)
- dragonwriter 13y agoGo was the previous language added to App Engine.
- orangethirty 13y agoMaybe they are forking it and calling it "Went"? I keed, I keed.
- phil 13y agoIs it OCaml? I bet it's OCaml.
- inovator 13y agoPHP or Ruby probably
- tnuc 13y agoI am honestly surprised it took this long. 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?
- dragonwriter 13y agoJRuby and Rails, AFAIK, have been able to run on the Java runtime for quite some time.
- braum 13y agojust throwing this in the hat, C# and .NET. It's possible...
- forgotAgain 13y agoI was thinking C# (mono) as well. My second guess would be Javascript. Looking in existing runtimes for hints is cheating.)
- rocky1138 13y agoHere's hoping it's 6502 assembly.
- glurgh 13y agoYou probably want its successor, the 65c816. Has a handy single instruction for getting a first pass of your web app running - MVP.
- hosay123 13y agoWoah, desperate much? 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!
- notatoad 13y agoAdding frequently requested features to your product is now "desperation"?
- alttab 13y agoIt is when you've ignored them forever. Why would you then be listening? Because you are trying to keep the users you have.
- dragonwriter 13y agoThe users AppEngine has now are, pretty much by definition, not the ones for whom PHP is a make or break feature. So that doesn't even make sense as explanation.
- biot 13y agoHow is App Engine as a product currently unjustified?
- chatmasta 13y agoI'm sure they verified before making this decision that the income from these new PHP customers will surpass the maintenance cost. Also consider that this decision may not even affect Google's costs, because they have enough maintenance engineers idling at any given time to assign to App Engine PHP maintenance.
- dragonwriter 13y ago> Woah, desperate much? 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.
- whalesalad 13y agoSpeaking of PHP in the clouds... fun fact: you can push PHP files to Heroku and they'll "just work". 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 Now enjoy your insanely simple + free PHP hosting. I was pretty excited and surprised when I discovered this.
- StavrosK 13y ago> Now enjoy your insanely simple + free PHP hosting. "Simple" and "free", sure, but "enjoy"?
- boyter 13y agoAs much as I dislike PHP as a language I am still insanely productive in it for dynamic websites. I enjoy being productive more then I enjoy using the latest languages/frameworks. So yes. I enjoy using PHP for all its faults.
- StavrosK 13y agoI feel a bit bad for taking that cheap shot at PHP, to be honest. We're all adults, and you should use whatever makes you more productive. A good programmer can write maintainable code in any language. However, "productive" and "latest frameworks/languages" is a bit of a false dichotomy.
- boyter 13y agoI agree. But I have seen many programmers claim they will be more productive in language/framework X because its new. 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.
- 13y ago
- sktrdie 13y agoWell according to GitHub it's either JavaScript or Ruby (PHP is only 6th) https://github.com/languages https://github.com/languages
- Kudos 13y agoGithub is a representative sample of published open source software, not of code being used in production.
- sktrdie 13y agoRight and that's what I meant, by saying "according to GitHub".
- draegtun 13y agoWell if Google was following their GAE issue list then it will most likely be PHP (#1 3274 stars) followed by Perl (#2 2246 stars) and then Ruby (#3 2162 stars). ref: http://code.google.com/p/googleappengine/issues/list http://code.google.com/p/googleappengine/issues/list
- BHSPitMonkey 13y agoImplying that the 6th most popular language on GitHub can't qualify as "very popular"?
- Tawheed 13y agoJavascript
- antsam 13y agoasp.net!
- mvanveen 13y agoor "How I learned to stop worrying and love ruby."