EVERYONE:  Please don't comment just to say "+1"; you're dropping emails in everyone
else's boxes when you do.  Just hit the star, and Google'll get the message.  :)

(Not a Google employee, just another Perl lover like everyone else!)

(No comment was entered for this change.)

So let's recap (I'll assume that Perl will happen, just to make the phrasing simpler)
because I don't see a Google admin going through every post in this thread to harvest
needs. Perl 5.10 comes with a good spread of starting modules. To that, we're
requesting the following modules and their associated dependencies:

+ CGI::Application
+ Catalyst
+ DBIx::Class
+ Template Toolkit (TT::Template)
+ HTML::Template
+ SOAP::Lite
+ POE

Please note that asking for low-level modules like mod_perl, LWP, Compress::Zlib and
so forth is fairly moot, as such modules are actually required for many of the above.
Catalyst alone pulls in a huge number of required modules.

I'd also like to collect a brief list of modules which I'm pretty certain won't be
required at any point (almost all related to interactive user-interfaces):

- Curses
- Gtk
- Tk
- Expect (maybe)

And then there are the modules that I'd love to see, but which represent substantial
work on some platforms. The only one I can think of is:

Math::Pari (on which Crypt::Random depends)

1) AGAIN! Stop those stupid "+1" or "add perl!" messages.  
thank you. As it's just one click to un-star this issue (far less than adding a 
filter to my email app) PLS: do not "+1" again.

2) since perl w/o cpan is only half (or whatever quote) as cool as a pure Perl 5.10 
core, I think a "request CPAN module for installation" mechanism or something like 
that would be very handy.

Perl support would indeed be a plus.  It would be helpful to know the specific needs of the sandbox and the 
particular rationale in the Python support for excluding extensions written in C.  The Perl core includes many 
extensions written in C and typically built as separate shared libraries and loaded at run-time.  While it's not a 
big deal to link them in statically, I suspect that's not the whole story.  What is the whole story, what particular 
syscalls must be blocked from the sandbox, how to begin auditing the code for what must be included or 
excluded, and so on, are all discussion worth having.  As Nicholas Clark said earlier here, write us at perl5-
porters@perl.org and let us know if there's something that needs to be done in the Perl core to make this 
possible.

Star this issue if you're interested in showing your support and tracking it. Don't
post "+1" comments: They make for a ton of spam, and will be immediately deleted.

I've gone through and deleted all existing "+1" comments, along with some of the
general Perl commentary posts. Feel free to contact me with any questions regarding
comment deletion.

Yes folks please stop with the +1 comments!  Show interest/support by starring it, or
say something if you have something to say, other than that please leave my inbox
alone :-)

Hi,

It is clear from the modifications that were made to Python in order for it
to be supported that there is a fair bit of language modification required.
Furthermore, Guido van Rossum joined the AppEngine team.

In order for Perl to ever be supported, it is probable that core members of 
the Perl community would need to be mobilized to support that effort.

I would like to see this project get organized and get off the ground.
I am volunteering to spearhead it (at least until someone better capable
of doing it volunteers) and mobilize members of the Perl community who
can assist with this. (i.e. to create a version of Perl, a set of libraries,
and a collection of frameworks with sufficient features disabled and sufficient
additional support added for BigTable, etc.)

However, I need an organizing contact at Google to coordinate with.
If there is any possibility of this working out, please let me know who that
would be.

Thanks,

Stephen Adkins
spadkins@gmail.com

P.S. YAPC::NA 2008 is coming up (in Chicago) in June, and this would be
an ideal time to advance such a project through its organizational phases.
So there is some aspect of this that is time-critical.

Stop the +1 spam please, I'm getting sick of it! Is everybody really too stupid to
read the messages above this comment form? -_-"

IN THE NAME OF ALL THAT IS HOLY, STOP WITH THE +1 AND ME-TOO POSTS!!!!

Just click on the star to show your support. All you do by spamming the list is make
people want to unstar it, which is completely counter-productive.

(sorry for shouting, just hoping to get people's attention *before* they +1.)

When a message arrives that matches the search: subject:(Issue 34 in 
googleappengine), do the following:

* Skip the Inbox (Archive it)

Keep your star on AND avoid the pointless +1 messages.

I would like to see Perl as a supported language.

Hi,

I have been promoting the idea of a community project to get Perl
supported on Google App Engine.

  http://code.google.com/p/googleappengine/issues/detail?id=34#c436

I have made various contacts with people inside Google, and it seems that the core
App Engine team is busy with plenty of other thinigs.  However, this does not stop
the community from getting something started.  We will likely attract perl advocates
within Google as we go along, even if they are not on the App Engine team.  I would
like to see the effort advance until the point where it becomes a simple matter for
the App Engine team to embrace Perl.

I have started a project for all people interested in following this effort or
contributing toward it.

  http://code.google.com/p/perl-appengine/

Please visit the website, sign up for the mailing list, spread the word, and start
contributing.

Thanks,

Stephen Adkins
spadkins@gmail.com

I would like to see Perl as a supported language too. Thanks!

Perl was the first serious language programming at Web-land, please, consider it.

Adding Perl to App Engine is now a community project and has begun.  See:

http://brad.livejournal.com/2388824.html

and Stephen Adkins has given me access to use the project he'd created, so we'll coordinate all our efforts at:

http://code.google.com/p/perl-appengine/

(No comment was entered for this change.)

It would be great to add perl support.

please add perl support

please add perl support

perl is the father of the Internet

hey people, what do you think about catalyst possibilities ?

 _                _    _ 
| |    ___   ___ | | _| |
| |   / _ \ / _ \| |/ / |
| |__| (_) | (_) |   <|_|
|_____\___/ \___/|_|\_(_)

Work on this is already underway, so please go to the project page to discuss (see
comment 463).

-1, stay on python and add features. no reason for other languages

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Please add Perl support, it will enhance Google App...

+1

Per support should definitely be added!

how to add stars

oh~~~my got

Before adding support for Perl, Google should definitely do something against
spammers and trolls.

ghs.google.com has been blocked in some countries, which means that your 
users/clients in these countries are not able to access your GAE services with your 
own domain name.

See http://code.google.com/p/googleappengine/issues/detail?id=1269 for more details.

please

There's a reason why perl is still around... please add support.

although i'm parroting others, please add perl support

Please ad Perl support, definitely a must.

What's involved in adding support for Perl? e.g. what are the stumbling blocks /
hurdles that need to be resolved in order to get it running in google app engine?

Please add perl support...

Please add perl support!

Would like to see perl support as well though I've tried not to parrot others.

if you wanna perl support, please, use:
http://code.google.com/p/perl-appengine/

One nice benefit to adding perl support is also adding anything supported by Inline 
as well. That would provide a simple, flexable interface to C, C++, Java, Python, 
Tcl (that I can think of).

Once we have Perl, the ability to add Catalyst, Moose, et al, becomes a simple 
enough matter. Being able to combine DBI or DBIx with the Google engine would be 
rather handy. 

The point is that Perl gives us all of this in one package.

I don't imagine that Inline would be supported - it requires, e.g. a C compiler.

please add perl support

please add perl support thanks

Please add support to the Google engine for Perl.

Please add Perl support to google engine.

Please add Perl support to google engine.

Please add Perl support to the Google Engine!

Please add Perl support to the Google Engine!

use Perl or die!

Please add Perl support to the Google Engine!

Please add Perl support to the Google Engine!

Perl must go on! :)

use Perl or die;

Just F*cking Do It

Please add perl support!
I really need it!

Please add Perl support to the Google Engine!

Please add perl support!
I really need it!

I'm unticking the star because I'm sick of getting an email every time some total
idiot enters "Add perl support!"

Perl - very well, it's my native language!

I need perl support too.

Please add perl support to the Google Engine!

use Perl or die!

Yes!

Perl support would be helpful.

I would like to see Perl as a supported language too. Thanks!

OH . . . MY . . . GOD!

Please, just click on the star at the top of this page next to "Issue 34: Add Perl
support". YOU DON'T NEED TO LEAVE A COMMENT!

If you're a Perl programmer why not consider helping the Perl AppEngine project at
http://code.google.com/p/perl-appengine/ so that Perl support is added sooner!

@eyescabs, use settings http://code.google.com/hosting/settings

sss

Please add Perl support to the Google Engine!

add perl please!!!

zzz

pearl in weights

Please add perl support!

Wx and AnyEvent... please!

I would like to see Perl as a supported languag

it will be cool :)

pawaperl

Please add perl support!
Plz!!!!

add perl support!!!

add perl, you bastards!!!

Regarding the suggestion in Comment 231 to add the "Catalyst" module: while
Catalyst::Runtime and Catalyst::Devel would be good, a real-world Catalyst
application will need more dependencies around Catalyst (plugins etc.). Installing
the MojoMojo module would pull all these in.

"+1"

Regarding the MojoMojo suggestion -- Isn't MojoMojo a whole application?
It is described as "A Catalyst & DBIx::Class powered Wiki." at
http://search.cpan.org/dist/MojoMojo/

I'm not sure it's appropriate to start including entire pre-made apps, is it?
Otherwise everyone will want their pet project included in the build too.

MojoMojo is indeed a Catalyst-powered wiki application, but Catalyst applications are
modules, so what I'm suggesting is having MojoMojo's dependency chain installed, not
necessarily MojoMojo per se.

It's been a while since I did any heavy duty perl, but I tend to agree with dryfter -
we don't want everyone's favourite included.

But we do want the "vanilla" system to be functional out of the box; and we want a
way to add the dependencies our project has (within the limits of App Engine).

I would suggest taking a look at what some ISP's offer as their basic perl offering
as a starting point.

Well, probably part of the problem which is why Perl had problems compared with say
PHP is that ISP offerings were generally rubbish for hosting serious Perl
applications.  And most of the big Perl sites were self-hosted (ie, dedicated
hardware).  It was never really for "Personal Home Pages".  Whereas PHP just linked
every C library under the sun into the process (like Apache does) and exposed them,
and encouraged people to ship libraries in their webroot.  Meaning getting PHP apps
running was always just a 'unpack a tarball into the webroot and go to configure.php'.

Certainly a good 'acceptance' test for reasonable Perl support would how easy it is
to use some of the more evolved applications out there;

  - Request Tracker and the Jifty framework
  - the Movable Type wiki
  - HTML::Mason - a bit 'old school' but still used!
  - Catalyst and DBIx::Class based applications like MojoMojo or Angerwhale, as
people have mentioned
  - Moose applications

No doubt you will find many people willing to help from the Perl community.  Michael
Schwern is a good default contact for referring you to the right person.

Ideally these systems would be available as off-the-shelf groups based on stable
released versions of modules so that people can just grab them and start, though
people should still be able to install updated versions of them to local library
directories.

My 2¢..

  The most merciful thing in the world ...  is the inability of the
human mind to correlate all its contents.
H P LOVECRAFT

Ah, the whole crew's already there - see http://code.google.com/p/perl-appengine/

Please add perl support!
It very important!!! Perl is cool!

As a perl programmer, I strongly propose that App engine support PERL!
Perl is a good language to write web applications, because it has so many mature 
libs like CGI. Also there are some web frameworks.

Please consider it.

Perl is good.
Please not ignore it.

Please add perl support!

Perl Please!

Please add Perl!!! The easiest and convenient language!! 

I endorse Comment 482  by fatfreddysays on May 22, 2009. But want to add that there
are actually MANY reasons why Perl is so great. Being one of them CPAN, where you can
find other MANY reasons more (excellent libs, doc, etc.). If you ever tried Perl and
know about PHP, Phyton etc (also if you take a look at articles about them all,
you'll possible find many reasons more. ie: who's 'father' of who.
here's another reason: Perl's father @ Google Tech talks ->
http://www.youtube.com/watch?v=JzIWdJVP-wo
Big hug to Larry Wall. 
long life to Perl and Javascript (the other masterpiece of web tech)

perl is a must