Even Python considered easy but a lot of developers still prefer PHP.
I wondering why Google preview this service while it only support one
programming language. This service is not ready for anything even for
preview. I hope during this preview period Google will add support PHP
and Ruby On Rails. You will have to think twice if you want to migrate
your apps to this service. When your apps is succesful , almost no
company will be willing to purchase your idea because of the high cost
of migrating that code out of Google even you have a large pool of
users. Except Google itself. Be careful..
In short, scaling out is hard to do. Scaling out with a multiplicity of engines is even harder. They are doing what any good software team will do - limit scope so as not to explode.
RoR and PHP are both very SQL orientated, and neither are Google native programming languages. Porting RoR over GAE means a fairly serious rejigging of ActiveRecord.
On Wed, Apr 9, 2008 at 10:16 PM, babylon <babylon2...@gmail.com> wrote:
> Even Python considered easy but a lot of developers still prefer PHP. > I wondering why Google preview this service while it only support one > programming language. This service is not ready for anything even for > preview. I hope during this preview period Google will add support PHP > and Ruby On Rails. You will have to think twice if you want to migrate > your apps to this service. When your apps is succesful , almost no > company will be willing to purchase your idea because of the high cost > of migrating that code out of Google even you have a large pool of > users. Except Google itself. Be careful..
I think allot of developers would like to see the big three (Python,
PHP, RoR) supported in AppEngine, but considering how the sandboxing
has to occur in regards to feature sets, adding a language could be a
monumental undertaking.
PHP in particular has a massive amount of functionality included out
of the box. Allot of python's power comes from it's libraries, so
making modifications gives developers options in adding abstraction
between their app and the Google specific SDK. Most PHP apps are build
on the core PHP functionality, making abstraction more inconvenient
for developers and more difficult for proper sandboxing.
If anything, PHP would be the most likely second candidate for
AppEngine, as it is the most popular web development language at the
moment. Hordes of developers would be looking to port applications
when it became available.
On Apr 9, 8:16 am, babylon <babylon2...@gmail.com> wrote:
> Even Python considered easy but a lot of developers still prefer PHP.
> I wondering why Google preview this service while it only support one
> programming language. This service is not ready for anything even for
> preview. I hope during this preview period Google will add support PHP
> and Ruby On Rails. You will have to think twice if you want to migrate
> your apps to this service. When your apps is succesful , almost no
> company will be willing to purchase your idea because of the high cost
> of migrating that code out of Google even you have a large pool of
> users. Except Google itself. Be careful..
I would have to agree with you on PHP most likely being the 2nd
support language. PHP would be a lot easier to implement, then again
just supporting the Ruby language and not Rails would be A LOT easier!
I really hope Ruby support (with or w/o Rails) comes really soon!
On Apr 9, 8:50 am, Newman Hunter <concept...@gmail.com> wrote:
> I think allot of developers would like to see the big three (Python,
> PHP, RoR) supported in AppEngine, but considering how the sandboxing
> has to occur in regards to feature sets, adding a language could be a
> monumental undertaking.
> PHP in particular has a massive amount of functionality included out
> of the box. Allot of python's power comes from it's libraries, so
> making modifications gives developers options in adding abstraction
> between their app and the Google specific SDK. Most PHP apps are build
> on the core PHP functionality, making abstraction more inconvenient
> for developers and more difficult for proper sandboxing.
> If anything, PHP would be the most likely second candidate for
> AppEngine, as it is the most popular web development language at the
> moment. Hordes of developers would be looking to port applications
> when it became available.
> On Apr 9, 8:16 am, babylon <babylon2...@gmail.com> wrote:
> > Even Python considered easy but a lot of developers still prefer PHP.
> > I wondering why Google preview this service while it only support one
> > programming language. This service is not ready for anything even for
> > preview. I hope during this preview period Google will add support PHP
> > and Ruby On Rails. You will have to think twice if you want to migrate
> > your apps to this service. When your apps is succesful , almost no
> > company will be willing to purchase your idea because of the high cost
> > of migrating that code out of Google even you have a large pool of
> > users. Except Google itself. Be careful..
I hate to think how much code would have to be audited in the php code base to make sure that the php code being run isn't impacting the runtime environment.
> I would have to agree with you on PHP most likely being the 2nd > support language. PHP would be a lot easier to implement, then again > just supporting the Ruby language and not Rails would be A LOT easier! > I really hope Ruby support (with or w/o Rails) comes really soon!
> On Apr 9, 8:50 am, Newman Hunter <concept...@gmail.com> wrote: > > I think allot of developers would like to see the big three (Python, > > PHP, RoR) supported in AppEngine, but considering how the sandboxing > > has to occur in regards to feature sets, adding a language could be a > > monumental undertaking.
> > PHP in particular has a massive amount of functionality included out > > of the box. Allot of python's power comes from it's libraries, so > > making modifications gives developers options in adding abstraction > > between their app and the Google specific SDK. Most PHP apps are build > > on the core PHP functionality, making abstraction more inconvenient > > for developers and more difficult for proper sandboxing.
> > If anything, PHP would be the most likely second candidate for > > AppEngine, as it is the most popular web development language at the > > moment. Hordes of developers would be looking to port applications > > when it became available.
> > On Apr 9, 8:16 am, babylon <babylon2...@gmail.com> wrote:
> > > Even Python considered easy but a lot of developers still prefer PHP. > > > I wondering why Google preview this service while it only support one > > > programming language. This service is not ready for anything even for > > > preview. I hope during this preview period Google will add support PHP > > > and Ruby On Rails. You will have to think twice if you want to migrate > > > your apps to this service. When your apps is succesful , almost no > > > company will be willing to purchase your idea because of the high cost > > > of migrating that code out of Google even you have a large pool of > > > users. Except Google itself. Be careful..
On Wed, Apr 9, 2008 at 6:26 PM, Brett Morgan <brett.mor...@gmail.com> wrote:
> I hate to think how much code would have to be audited in the php code > base to make sure that the php code being run isn't impacting the > runtime environment.
> On Thu, Apr 10, 2008 at 1:05 AM, Chris Ledet > <christopher.le...@gmail.com> wrote:
> > I would have to agree with you on PHP most likely being the 2nd > > support language. PHP would be a lot easier to implement, then again > > just supporting the Ruby language and not Rails would be A LOT easier! > > I really hope Ruby support (with or w/o Rails) comes really soon!
> > On Apr 9, 8:50 am, Newman Hunter <concept...@gmail.com> wrote: > > > I think allot of developers would like to see the big three (Python, > > > PHP, RoR) supported in AppEngine, but considering how the sandboxing > > > has to occur in regards to feature sets, adding a language could be a > > > monumental undertaking.
> > > PHP in particular has a massive amount of functionality included out > > > of the box. Allot of python's power comes from it's libraries, so > > > making modifications gives developers options in adding abstraction > > > between their app and the Google specific SDK. Most PHP apps are > build > > > on the core PHP functionality, making abstraction more inconvenient > > > for developers and more difficult for proper sandboxing.
> > > If anything, PHP would be the most likely second candidate for > > > AppEngine, as it is the most popular web development language at the > > > moment. Hordes of developers would be looking to port applications > > > when it became available.
> > > > Even Python considered easy but a lot of developers still prefer > PHP. > > > > I wondering why Google preview this service while it only support > one > > > > programming language. This service is not ready for anything even > for > > > > preview. I hope during this preview period Google will add support > PHP > > > > and Ruby On Rails. You will have to think twice if you want to > migrate > > > > your apps to this service. When your apps is succesful , almost no > > > > company will be willing to purchase your idea because of the high > cost > > > > of migrating that code out of Google even you have a large pool of > > > > users. Except Google itself. Be careful..
On Thu, Apr 10, 2008 at 11:47 AM, Lee O <lee...@gmail.com> wrote: > Blech, google is python, what do you expect? :)
> Not that this is a bad thing imo, i love python, and im loving Google App > Engine
> On Wed, Apr 9, 2008 at 6:26 PM, Brett Morgan <brett.mor...@gmail.com> wrote:
> > I hate to think how much code would have to be audited in the php code > > base to make sure that the php code being run isn't impacting the > > runtime environment.
> > On Thu, Apr 10, 2008 at 1:05 AM, Chris Ledet > > <christopher.le...@gmail.com> wrote:
> > > I would have to agree with you on PHP most likely being the 2nd > > > support language. PHP would be a lot easier to implement, then again > > > just supporting the Ruby language and not Rails would be A LOT easier! > > > I really hope Ruby support (with or w/o Rails) comes really soon!
> > > On Apr 9, 8:50 am, Newman Hunter <concept...@gmail.com> wrote: > > > > I think allot of developers would like to see the big three (Python, > > > > PHP, RoR) supported in AppEngine, but considering how the sandboxing > > > > has to occur in regards to feature sets, adding a language could be a > > > > monumental undertaking.
> > > > PHP in particular has a massive amount of functionality included out > > > > of the box. Allot of python's power comes from it's libraries, so > > > > making modifications gives developers options in adding abstraction > > > > between their app and the Google specific SDK. Most PHP apps are > build > > > > on the core PHP functionality, making abstraction more inconvenient > > > > for developers and more difficult for proper sandboxing.
> > > > If anything, PHP would be the most likely second candidate for > > > > AppEngine, as it is the most popular web development language at the > > > > moment. Hordes of developers would be looking to port applications > > > > when it became available.
> > > > > Even Python considered easy but a lot of developers still prefer > PHP. > > > > > I wondering why Google preview this service while it only support > one > > > > > programming language. This service is not ready for anything even > for > > > > > preview. I hope during this preview period Google will add support > PHP > > > > > and Ruby On Rails. You will have to think twice if you want to > migrate > > > > > your apps to this service. When your apps is succesful , almost no > > > > > company will be willing to purchase your idea because of the high > cost > > > > > of migrating that code out of Google even you have a large pool of > > > > > users. Except Google itself. Be careful..
Honestly, do yourself a favor and spend half an hour with the python
tutorial and the interpreter running.
You will ask yourself why you waisted so much time with that
abomination called PHP...
On 9 abr, 09:16, babylon <babylon2...@gmail.com> wrote:
> Even Python considered easy but a lot of developers still prefer PHP.
> I wondering why Google preview this service while it only support one
> programming language. This service is not ready for anything even for
> preview. I hope during this preview period Google will add support PHP
> and Ruby On Rails. You will have to think twice if you want to migrate
> your apps to this service. When your apps is succesful , almost no
> company will be willing to purchase your idea because of the high cost
> of migrating that code out of Google even you have a large pool of
> users. Except Google itself. Be careful..
> Even Python considered easy but a lot of developers still preferPHP.
> I wondering why Google preview this service while it only support one
> programming language. This service is not ready for anything even for
> preview. I hope during this preview period Google will add supportPHP
> and Ruby On Rails. You will have to think twice if you want to migrate
> your apps to this service. When your apps is succesful , almost no
> company will be willing to purchase your idea because of the high cost
> of migrating that code out of Google even you have a large pool of
> users. Except Google itself. Be careful..
On Mon, Apr 14, 2008 at 9:14 PM, Michael Tsyganov <mich...@bobrdobr.ru> wrote:
> Just get PHP-Interpreter writte in Python
> On Apr 9, 2:16 pm, babylon <babylon2...@gmail.com> wrote: > > Even Python considered easy but a lot of developers still preferPHP. > > I wondering why Google preview this service while it only support one > > programming language. This service is not ready for anything even for > > preview. I hope during this preview period Google will add supportPHP > > and Ruby On Rails. You will have to think twice if you want to migrate > > your apps to this service. When your apps is succesful , almost no > > company will be willing to purchase your idea because of the high cost > > of migrating that code out of Google even you have a large pool of > > users. Except Google itself. Be careful..
On Apr 9, 2:50 pm, Newman Hunter <concept...@gmail.com> wrote:
> I think allot of developers would like to see the big three (Python,
> PHP, RoR) supported in AppEngine, but considering how the sandboxing
> has to occur in regards to feature sets, adding a language could be a
> monumental undertaking.
Then what is Java? The "gigantic one"?
Anyway, I think it's obvious that if Google AppEngine team wrote about
"more languages" to be supported in AppEngine itself, it means that
they already know how to proceed.
Anyway, it would be really nice to have some Google comment about how
the runtime works, and what's boiling in the GAE craddle.
> Honestly, do yourself a favor and spend half an hour with the python
> tutorial and the interpreter running.
> You will ask yourself why you waisted so much time with that
> abomination called PHP...
I read article about google few years ago. It was said that python and
java are most favorable languages in google.
This article was on sun's sites and mostly was written about google's
experiences switching from java 1.4 to java 5.
Do you really know if it is python? It could be Jython.
If I am right then next language could be Groovy, BeanShell or JRuby.
On Tue, Apr 15, 2008 at 1:03 AM, max7 <max.seven....@gmail.com> wrote:
> I read article about google few years ago. It was said that python and > java are most favorable languages in google. > This article was on sun's sites and mostly was written about google's > experiences switching from java 1.4 to java 5.
> Do you really know if it is python? It could be Jython. > If I am right then next language could be Groovy, BeanShell or JRuby.
