views:

264

answers:

1

I've heard of GAE and even though it doesn't support PHP, people have gotten around this limitation by using Quercus I think (I haven't tried it, but supposedly it works). But what factors should I consider when evaluating whether it's a match for me? For example, what made you not go with GAE? Or if you went with it, what are you not happy about?

thanks

Edit:

Thanks to those who saw value in the question and defended it. I've seen questions here that were much less programming-related than mine and which were left open. In terms of it being a dupe, it isn't in anyway. That other question was specifically about PHP support; mine is about why not GAE in general (the php was a sidenote). I doubt the guy that yelled "dupe" even read both questions to see how mine is obviously so much different. You can vote it reopened if you still see value in it. Some good answers were already coming in, too bad the 5 of you killed a Perfectly Good Thing. I voted for a reopen, 4 more people could hop on if interested.

+1  A: 

Because GAE is less flexible and tightly coupled to Google's framework.

jpartogi
Less flexible than what?
ChssPly76
Less flexible than deploying it to a VPS.
jpartogi