I am creating Perl tutorial site for newbie "Sampuru codo ni yoru perl nyuumon"
I am creating Perl tutorial for newbie "Sanpuru codo ni yoru perl nyuumon"(Perl Tutorial by code examples)
Sampuru codo ni yoru perl nyuumon
This is site for perl newbie.
I hear that perl is dirty, not cool, very loose. Ruby is good, python is good.
But Perl is good language.
Perl have ability to write code clean and beatutiful.
For example, Mojolicious have clean code.
This is perl.
The big reason perl is said dirty is perl very old code which is more than ten years old.
In the old days, non-programer write perl code for CGI script to create Web site.
The old perl code is dirty, but latest perl code is not dirty.
Perl is fast, light, and stable, less-memory.
I think Perl need more understandable tutrial which have examples.
I'm Perl Programmer. I LOVE Perl. I want to contribute Perl community and Perl users.
Thanks a lot for writing this tutorial! :)
I looked it over with Google Translate and it looks pretty good.
I also added it to http://perl-tutorial.org/ . Please take a look and correct any mistakes i made in the data about it. :)
Great work so far, and good luck building your site!
Yes, I think Perl can be very beautiful, particularly if you let Perl be Perl and not try to force paradigms from other languages.
--John
>Mithaldu
Thanks. Target is Perl 5.8. Cover is Perl Basic + Advanced(DBI, Web framework, Object-Oriented, and etc).
Size is large(more than 500 pages)
> john napiorkowski
Perl is good, but many people think perl is worse than ruby and python. this is misleading message.
Perl have many good features. Perl support many os and is installed in many os by default. development speed is fast. Applications which is create by perl is easy to install. Perl is stable, so one source code work well in various perl version.
Hm, why 5.8? I thought major Perl distros have moved on to 5.10 or 5.14 at least. This includes Debian/Ubuntu and RHEL/CentOS.
Sadly, I think Perl 5.8 *is* worse than Ruby and Python. Out-of-date Unicode support, no regex named captures, no possessive quantifiers, no say()...
I agree with Steven Haryanto. The Perl core guys have made several statements saying only the last two releases of Perl are officially supported by the community. This means if you are running anything older than 5.16, you're using an officially "old" and "unsupported" version of Perl.
Why did you choose 5.8 as your target? Is it because that's what is installed with your operating system (as is the case with RHEL/CentOS 5?)
If you ignore everything since 5.8, you also dodge the smart match and lexical $_ debacles. For a tutorial, I doubt many of the other new features matter.
On a completely unrelated note... I guess "sampuru" is a Japanese pronunciation of the English word "sample." From the bit of French I know, English seems to be adopted for new terms like "chewing gum," but I'm surprised that Japanese adopted the English word for "sample". Do you know anything about the etymology?
>Steven Haryanto
I'm very conservative. CentOS5 is yet used in the world. and most cpan perl modules support Perl 5.8.
Unicode support is enough collect in Perl 5.8.7.
regex named captures is broken until perl 5.16 (it have memory leak).
>Doran "Fozz" Barton
I'm yet use CentOS5 in my work. Perl community don't support old perl, but most important thing is user actual benefit, not ideal.
If you are application author in your jobs, I recommend latest perl. but if you are module author or portable application author, I yet recommend Perl 5.8.7.
Japanese use the word "sample"(サンプル) as English "example" meaning. I don't know etymology. サンプル is maybe Japanese-English word. this word is often used.
Choosing v5.008 makes sense as lot of the Japanese CPAN modules also default to a minimum of v5.008 (see for example tokuhirom's Minilla.) Furthermore, there are still some places where you can't just perlbrew up a more modern version, so make do with what's available ;)
FWIW Mojolicious also has a legacy fork that runs on v5.008.
Thanks for the notes, i updated the data. :)
For you, for the future: When you next update the tutorial, you can easily edit the data yourself by logging in on the site with almost any OpenID provider.
thank, i had'nt known your site can use open id.