4 ms·
Woah, 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
by hosay123 13y ago
Woah, 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.
- mvanveen 13y agoTo this end, did anyone suggest Heroku was a dying platform when they announced Python support? I sure didn't hear anything like that.