On 8 July 2011 12:28, Rajeev Prasad <rp.ne...@yahoo.com> wrote:
> will apps made for one distribution of Rakudo work with another?

Yes, provided that the versions of Rakudo used are sufficiently
compatible (one might have newer features that you used that another
one hasn't updated to include yet, for example), and that the required
modules are available. I don't imagine that we'll get into a situation
where you install one particular distribution and then can't install
the modules bundled with a different one.

> the time for web targeted distro is approaching fast. as soon as we know the 
> most secure/stable and extendable WEB services 
> model(mashups/REST/XML/WSDL...) is identified/spec-ed, there will be a need 
> (requirement) for perl compiler(or any other SSLanguage) to support it out of 
> the box.
> - i think so.

Web programming is one of the big applications for Perl historically.
It would be silly to neglect that for Perl 6, and there are people
looking at writing the necessary modules to provide the support. I
wouldn't be at all surprised to see at least a basic CGI module in
Rakudo Star. I wouldn't expect something like Catalyst though - that's
a bit big to bundle in, but would instead be installed separately. I
would also not expect to find this functionality put into the core
language at any point - Perl 6 is deliberately intended to be powerful
and flexible so that you can write good modules to do anything you
need to do without having to have core language support for
everything. That way, everybody gets what they need, whether they're
doing CGI programming or writing a compiler or using image recognition
to count the number of sweets in a jar.

You mention too many choices of modules confusing new users - yes,
that is a problem, but I personally prefer to have the ability to
choose the most suitable module for my task, rather than being stuck
with something that somebody has declared is the right way to do it,
but actually fits my use case quite badly and causes me a lot of
frustration as a result.

What is needed is a way to make the appropriate modules easy to find,
easy to get and easy to use, in a way that can make system
administrators happy (because I know CPAN drives them nuts).

> rgds,
> Rajeev
> ________________________________
> From: Carl Mäsak <cma...@gmail.com>
> To: "perl6-language@perl.org" <perl6-language@perl.org>
> Sent: Friday, July 8, 2011 6:05 AM
> Subject: Re: STDOUT = WWW
> Rakudo (the compiler) will be packaged in various distributions. The
> one distribution we have so far is Rakudo Star.
> There's sometimes been talk on conferences and on IRC about putting
> together a Net/Web-targeted distribution of Rakudo, one with all the
> appropriate modules pre-packaged. The idea is sound; its time may or
> may not have arrived.
> // Carl
> On Fri, Jul 8, 2011 at 12:59 PM, Rajeev Prasad <rp.ne...@yahoo.com> wrote:
>>> perl generates the WWW page and dynamic form for WWW user, using data 
>>> stored in RDBMS.
>>> WWW user fills form on browser
>>  >form runs a perl script on server
>>    > perl script saves input data in RDBMS
>>    > perl script logs into many other heterogeneous systems using advertised 
>> web-services, ssh, telnet etc..
>>    > perl script fetches data, operate on it. and saves it in RDBMS
>>       > output it back to WWW user with proper presentation
>> this is going to be the most used scenario (of perl6) in future[in other 
>> words STDOUT=WWW, and STDIN = WWW/RDBMS/remote sys(RPC)], therefore my
>> request is to have some basic (tested fast/secure) functionality built
>> into the base language(interpreter itself), so that i do not have to use any 
>> modules for
>> such activity.
>> Of-course, there can be choice of modules of all of above and much
>> more, but for 80% population, basic setup is enough, which means high
>> popularity, and user-base. Too many choices in modules to do the same thing 
>> over and over again confuses new developers and slows down development. Also 
>> multiple modules doing the same thing, will overlap activities with other 
>> unrelated modules too. (But), you can not control how many modules will be 
>> written for a particular task (say for e.g. generating HTML templates). 
>> Therefore old timers and exceptional knowers of language should clearly rate 
>> modules and incorporate minimal functionality (as much as possible) into the 
>> base interpreter itself.
>> Another wish is, base interpreter should have no diff whether used to serve 
>> documents via console/non HTTP protocol or HTTP protocol.
>> all the best to perl6 community.
>> thank you.
>> rajeev

Reply via email to