Clear questions and runnable code
get the best and fastest answer
Re^2: Perl 6 and Web Developmentby jdrago_999 (Hermit)
|on Jun 18, 2009 at 04:22 UTC||Need Help??|
Perrin you definitely get my ++ here.
Maybe FastCGI is the way to go. Did I miss the bus on that? Is it the way of the future with regards to running Perl6 on the web?
And it's not about the price (for me anyways). It's about the widespread, default install base and availability. Perl6 might be the greatest thing since sliced bread but if you have to get root privileges to even get started, it will never catch on. At least not until Perl6 is installed by default on the most popular Linux distributions - which might not happen for at least another couple of years.
Perl Web Pages
The current crop of web dev systems are still in the stone ages. All of them without exception. Some may have moved ahead of the pack into the New Stone Age (with pottery and stick-figure paintings) but that's about it.
Not to worry. I feel the same way about Ruby on Rails, PHP and ASP.Net (Vanilla, MVC and AJAX).
I suppose the good news is that there is plenty of room for improvement. A Catalyst + Perl6 setup could be really slick. Add to that a Perl6 ORM layer and we're talking.
I'd like to get hacking on something - mostly just for the sake of learning Perl6 while doing something that interests me.
Perl6 Web Server
Do you know how hard it is to write a decent HTTP server?
It's been done in C at least a couple times. I'm sure it's possible in Perl. Just think of all the cool stuff you'll get:
Seriously - yes writing a secure, high-performance http server is not something to be taken lightly. At least part of the security problems in the http servers written in C were simply because they were written in C. Assuming that "somebody else" who knows what they're doing has already made sure that Parrot is secure (or *will* make it secure), writing an http server in Perl6 means that we instantly can run it on anything Parrot is ported to.
I was hoping 5 years ago that it would just *go away* but unfortunately we're stuck with it for the foreseeable future. Anything to make this a non-issue when integrating Perl systems with .Net or Java systems would be great.