ah... good old HN snobs tripping over each other in the comments section to give old PHP a much needed lashing.
Google App Engine finally supports PHP
21–30 of 80 posts
Re: Google App Engine finally supports PHP
#22This move doesn't make much sense to me. Most of the websites built in PHP are huge CMS services like Weebly, Wordpress, Joomla, or old social networks like Facebook. I don't see any of these large services switching over to get hosted on Google. Plus PHP in general is disorganized and slow compared to more contemporary languages with well defined frameworks.
Re: Google App Engine finally supports PHP
#23Google App Engine was almost a science project for the first few years, only supporting languages that Google used internally. Python?
Guido van Rossum (Python Inventor) worked at Google--That's why they went Python.
Re: Google App Engine finally supports PHP
#24 char* a = "PHP";
while (*a) putchar(*a+++7);Re: Google App Engine finally supports PHP
#25They seem to twist the facts ever so slightly. PHP is not "most popular computing language on the planet", it's the most popular web coding language; C is the most popular "computing" language, whatever that means. And in linked article they make it seem that PhoneGap apps are more native than they are, "built-in PhoneGap integration so developers can publish native app packages to the various app stores". Not factua…
I'd say that Java is the most popular one, but C does all the hard work!
Re: Google App Engine finally supports PHP
#26Earlier quoted context omitted.
But, what if it were the insane parts that made PHP successful? PHP is basically a shell script hooked up to a web server, with '$_REQUEST' flowing in one way, and 'echo' flowing out the other way. Its over-simplified architecture is exactly why beginners like it so much.
The simple architecture is actually what PHP got right. For comparison, if you were using mod_python with the default settings, you needed to restart apache whenever you changed a file. The insane part of PHP is the actual language. It's an overgrown template language. Half the functions are based on C, half the functions are based on Perl. There's no regularity or consistency.
Half the functions are based on C, half the functions are based on Perl. There's no regularity or consistency.
Recently, a third half of it was based on Java. :-)
Re: Google App Engine finally supports PHP
#27ah... good old HN snobs tripping over each other in the comments section to give old PHP a much needed lashing.
There's nothing "snobbish" about pointing out serious technological flaws in a given programming language or application. This is especially true when those flaws have no justifiable reason for existing in the first place, or when they can compromise the security of data and other systems.
Re: Google App Engine finally supports PHP
#28Re: Google App Engine finally supports PHP
#29More potential for one of the worst languages to spread - let's have one minute of silence. And after that someone please start building an alternative keeping the good parts that made PHP successful and getting rid of the insane stuff.
We get it, you don't like PHP. Move on already.
No, it's good for people to be extremely vocal about technologies riddled with serious flaws. It's unfortunate, but ultimately beneficial, even when they have to do this repeatedly.
It doesn't matter if we're talking about PHP or JavaScript, or a web framework like Ruby on Rails, or various NoSQL databases, or even certain operating systems.
Even if people have used such technologies with some degree of success in the past, and even if they may still be using them today, it's important for us to move past them, as a community and as an industry.
Making their flaws widely known is a very good step toward moving to better technologies. So I encourage people to be vocal about their bad experiences, or about the flaws they see in technology. It's an important part of advancement.
Re: Google App Engine finally supports PHP
#30ah... good old HN snobs tripping over each other in the comments section to give old PHP a much needed lashing.
There's nothing "snobbish" about pointing out serious technological flaws in a given programming language or application. This is especially true when those flaws have no justifiable reason for existing in the first place, or when they can compromise the security of data and other systems.
Right, but it doesn't need to be pointed out by 100 people every single time the language comes up in conversation. PHP has its place. HNs typical "PHP LOL OMFG WTF SHIT" reaction is childish.