Comments on: Why not PHP for Google’s App Engine? http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/ Web development and new media observations Sat, 13 Mar 2010 16:16:27 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Sanjeev http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-81642 Sanjeev Sat, 16 Jan 2010 11:54:40 +0000 http://michaelkimsal.com/blog/?p=500#comment-81642 No Need to Compare.Just matter of requirement matches with the Product. No Delay,When Google adopt PHP to develop any application. No Need to Compare.Just matter of requirement matches with the Product.
No Delay,When Google adopt PHP to develop any application.

]]> By: Bosko http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-80425 Bosko Fri, 25 Dec 2009 21:35:48 +0000 http://michaelkimsal.com/blog/?p=500#comment-80425 Python has very simple way of making multithreaded applications. Python engine itself is single threaded ( it has a GIL - Global Interpreter Lock ), but from time to time developer of C software can decide to leave interpreter and do some work outside Python, which allows some other thread to acquire the GIL and continue executing Python code. It's a very nice way of having single threaded scripting language to behave as if it's like C++. Most of the socket, file and other I/O is made non-blocking. Python has very simple way of making multithreaded applications. Python engine itself is single threaded ( it has a GIL – Global Interpreter Lock ), but from time to time developer of C software can decide to leave interpreter and do some work outside Python, which allows some other thread to acquire the GIL and continue executing Python code. It’s a very nice way of having single threaded scripting language to behave as if it’s like C++. Most of the socket, file and other I/O is made non-blocking.

]]> By: tejas http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-58715 tejas Tue, 24 Feb 2009 12:25:23 +0000 http://michaelkimsal.com/blog/?p=500#comment-58715 god knows.. i wanted to use google apps with as php is not supported it cant use it also.. god knows..
i wanted to use google apps with as php is not supported it cant use it also..

]]> By: 86geeker http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-53001 86geeker Sat, 29 Nov 2008 14:12:16 +0000 http://michaelkimsal.com/blog/?p=500#comment-53001 well,guido is really the big fator, because the python way is "simple is better," and it has a words says like this "There should be one-- and preferably only one --obvious way to do it." they are python user,so they think python as THE "preferably only one" BTH,if not guido but Larry works at google then i think google's appengine will support perl and many other language at first cause THE "TMTOWTDI" well,guido is really the big fator,
because the python way is “simple is better,” and it has a words says like this
“There should be one– and preferably only one –obvious way to do it.”
they are python user,so they think python as THE “preferably only one”
BTH,if not guido but Larry works at google
then i think google’s appengine will support perl and many other language at first
cause THE “TMTOWTDI”

]]> By: Jon http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-38374 Jon Wed, 02 Jul 2008 16:05:42 +0000 http://michaelkimsal.com/blog/?p=500#comment-38374 Python is an underrated language and Googles choice to push it is excellent. As a developer with a computer science background I find it easy to pick up and use any language. I often see intence arguements in blog comments along the lines of "my language is better than your language" and really feel that (as another commenter put it above) a langauge is just a tool and a good programmer uses the right tool for the job. I encourage any developers out there, who only develop in one language to give another language a try. Download and try App Engine, with Python you can achieve a lot with little code. I recommend looking at Django too in my personal opinion superior to Rails with a more programatic orm and better performance, with easier deployment. I for one am a (in no particluar order) PHP, Java, C#, Flex/Air (Actionscript), Javascript, Python, Ruby on Rails, Objective-C (to name a few) developer and really believe the more languages you learn the easier it is to pick up new ones and switch between languages. Not only will you add another string to your bow, you take away new ideas and practices that you can apply to your favorite languages. Python is an underrated language and Googles choice to push it is excellent. As a developer with a computer science background I find it easy to pick up and use any language. I often see intence arguements in blog comments along the lines of “my language is better than your language” and really feel that (as another commenter put it above) a langauge is just a tool and a good programmer uses the right tool for the job.

I encourage any developers out there, who only develop in one language to give another language a try. Download and try App Engine, with Python you can achieve a lot with little code. I recommend looking at Django too in my personal opinion superior to Rails with a more programatic orm and better performance, with easier deployment.

I for one am a (in no particluar order) PHP, Java, C#, Flex/Air (Actionscript), Javascript, Python, Ruby on Rails, Objective-C (to name a few) developer and really believe the more languages you learn the easier it is to pick up new ones and switch between languages. Not only will you add another string to your bow, you take away new ideas and practices that you can apply to your favorite languages.

]]> By: PHP Weekly Reader - April 13th 2008 : phpaddiction http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-33315 PHP Weekly Reader - April 13th 2008 : phpaddiction Tue, 15 Apr 2008 07:36:42 +0000 http://michaelkimsal.com/blog/?p=500#comment-33315 [...] love this — Why not PHP for Google’s App Engine? and Google App Engine needs PHP support… well why not any number of languages. Seriously if [...] [...] love this — Why not PHP for Google’s App Engine? and Google App Engine needs PHP support… well why not any number of languages. Seriously if [...]

]]> By: Michael J Caboose http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-33212 Michael J Caboose Sat, 12 Apr 2008 13:53:51 +0000 http://michaelkimsal.com/blog/?p=500#comment-33212 Google App Engine isn't limited to do other languages in the future. I would say you got the question back words, though, why PHP? Google App Engine isn’t limited to do other languages in the future.

I would say you got the question back words, though, why PHP?

]]> By: DiegoPires.net » O PHP precisa da nossa ajuda http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-33188 DiegoPires.net » O PHP precisa da nossa ajuda Fri, 11 Apr 2008 16:47:55 +0000 http://michaelkimsal.com/blog/?p=500#comment-33188 [...] Links sobre o assunto: http://www.phpclasses.org/blog/post/77-Google-App-Engine-needs-PHP-support.html http://www.securityspace.com/s_survey/data/200803/index.html?refid=1057382149 http://www.securityspace.com/s_survey/data/man.200803/apachemods.html?refid=1057382149 http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/ [...] [...] Links sobre o assunto: http://www.phpclasses.org/blog/post/77-Google-App-Engine-needs-PHP-support.html http://www.securityspace.com/s_survey/data/200803/index.html?refid=1057382149 http://www.securityspace.com/s_survey/data/man.200803/apachemods.html?refid=1057382149 http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/ [...]

]]> By: Google App Engine - When will programmers learn that a language is just a tool? at Urubatan’s Weblog http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-33185 Google App Engine - When will programmers learn that a language is just a tool? at Urubatan’s Weblog Fri, 11 Apr 2008 15:51:36 +0000 http://michaelkimsal.com/blog/?p=500#comment-33185 [...] big problem is that because App Engine is from Google, most of the developers that haven’t not learned Python yet are yelling around because Google App Engine does not [...] [...] big problem is that because App Engine is from Google, most of the developers that haven’t not learned Python yet are yelling around because Google App Engine does not [...]

]]> By: rabitguy http://michaelkimsal.com/blog/why-not-php-for-googles-app-engine/comment-page-1/#comment-33183 rabitguy Fri, 11 Apr 2008 13:27:40 +0000 http://michaelkimsal.com/blog/?p=500#comment-33183 There are many, many reasons why this discussion is silly. First of all, Google App Engine (like Amazon's AWS) is not a platform you can drop in an pre-existing webapp. Google wants you to develop your app using their architecture and API, so you will be more likely to stay with them. Google loves simplicity and the Google App Engine is simple. Their purely Python-based SDK is surprisingly easy to set up and to start testing/debugging your apps, and Python has exceptional interactive debugging. PHP would require them to include a large, native executable within the SDK, why should Google inconvenience all their customers because a small minority demand PHP? Last time I worked on a big PHP project, there were no freeware available tools for interactively debugging your PHP code. A large majority of PHP 'modules' must be natively compiled into the interpreter, where most modules for Python are implemented in Python code. There's no way Google will be able to cater to the needs of all PHP users, but Python users can integrate any module that doesn't rely on native extensions into their Google App Engine projects. And yes, PHP is a fully interpreted language while Python caches a compiled version of the code. Additionally, there are several projects for Python like Psyco or Psycotic that perform JIT-compilation into native code resulting in speed increases of up to 100x of Python's already pretty fast speed. This is I'm sure a big reason Google likes Python, and the very reason they can offer a service like Google App Engine, and by standardizing on Python, they can continue to tweak it's performance on their servers behind the scenes. All language syntax issues aside, the problem chiefly is that PHP *just does not apply here* here. Have any of you who are arguing for PHP even *looked* at how App Engine operates? Just download the free SDK. App Engine is a framework, like Ruby On Rails, that closely ties maps URL requests to classes/methods/functions and spits out data within templates. PHP was designed to embed small bits of code into static HTML. Yes, you can build an MVC framework on PHP (or Perl or Javascript or whatever) but the issue is PHP's architecture was not designed for that, and it just isn't suited to what Google is doing here. There are many, many reasons why this discussion is silly. First of all, Google App Engine (like Amazon’s AWS) is not a platform you can drop in an pre-existing webapp. Google wants you to develop your app using their architecture and API, so you will be more likely to stay with them. Google loves simplicity and the Google App Engine is simple. Their purely Python-based SDK is surprisingly easy to set up and to start testing/debugging your apps, and Python has exceptional interactive debugging. PHP would require them to include a large, native executable within the SDK, why should Google inconvenience all their customers because a small minority demand PHP? Last time I worked on a big PHP project, there were no freeware available tools for interactively debugging your PHP code.

A large majority of PHP ‘modules’ must be natively compiled into the interpreter, where most modules for Python are implemented in Python code. There’s no way Google will be able to cater to the needs of all PHP users, but Python users can integrate any module that doesn’t rely on native extensions into their Google App Engine projects.

And yes, PHP is a fully interpreted language while Python caches a compiled version of the code. Additionally, there are several projects for Python like Psyco or Psycotic that perform JIT-compilation into native code resulting in speed increases of up to 100x of Python’s already pretty fast speed. This is I’m sure a big reason Google likes Python, and the very reason they can offer a service like Google App Engine, and by standardizing on Python, they can continue to tweak it’s performance on their servers behind the scenes.

All language syntax issues aside, the problem chiefly is that PHP *just does not apply here* here. Have any of you who are arguing for PHP even *looked* at how App Engine operates? Just download the free SDK. App Engine is a framework, like Ruby On Rails, that closely ties maps URL requests to classes/methods/functions and spits out data within templates. PHP was designed to embed small bits of code into static HTML. Yes, you can build an MVC framework on PHP (or Perl or Javascript or whatever) but the issue is PHP’s architecture was not designed for that, and it just isn’t suited to what Google is doing here.

]]>