4 ms·
He seems to be saying "PHP shouldn't be supported because its a bit of an ugly language and somewhat insecure" But then should they only support Scheme? :] Th
by gord 18y ago
He seems to be saying "PHP shouldn't be supported because its a bit of an ugly language and somewhat insecure"
But then should they only support Scheme? :]
The problem is theres so much useful {badly written} PHP code out there, its going to be hard to ignore.
I guess they'll _have_ to adopt PHP, Python, Ruby/Rails in order to get user volume.
Which language is better is probably irrelevant.
- vetinari 18y agoActually, the amount of (badly written) PHP code works against PHP in this case. Not due to esthetic or subjective opinions about PHP, but for very pragmatic reason - SQL. AppEngine does not support SQL as we know it, but uses the google database and GQL. Changing that huge amount of PHP with interspersed SQL statements is not worth it. As for now, it supports Python and JVM languages (that includes JRuby). But even for these languages, third party libraries can be a problem. Edit: typo
- jlees 18y agoWell, the OP seems to point at PHP developers generally being poorly educated and clueless, mostly deploying other people's apps rather than writing their own. In short, they won't have a clue how to use GAE if it provides BigTable rather than MySQL so out-of-the-box LAMP apps fail to work without a rewrite. Does GAE really want user volume if those are the sorts of users they'll get?