Re^2: Summary of Perl in the past 2-3 years

I'm afraid it's going to be Perl providing CPAN to them and getting a few thingies in return. How much do you expect from the "There's only one way and it's the my way" pythonistas or the "oh we are so cute and clean" rubyists?

I'd like to be proved wrong.

Jenda
Enoch was right!
Enjoy the last years of Rome.

Comment on Re^2: Summary of Perl in the past 2-3 years

Replies are listed 'Best First'.
Re^3: Summary of Perl in the past 2-3 years by webfiend (Vicar) on Apr 22, 2010 at 18:52 UTC
I think that's a broad brush being used to paint Python and Ruby devs. The Zen of Python mentions "There should be one-- and preferably only one --obvious way to do it." There can be multiple solutions, but one of them should be obvious to experienced Pythonistas. Experienced Ruby coders have no illusions about the language being cute or clean - they recognize the warts of the language, but still prefer to work within its world where every value is an easily inspected / modified object. A super-CPAN could be a nice thing to have. I would be a happy camper if I could easily access Python-Markdown or the Seattle.rb projects from within my Rakudo app.	[reply]
Re^3: Summary of Perl in the past 2-3 years by jethro (Monsignor) on Apr 22, 2010 at 16:17 UTC
At least in the area of web frameworks perl could profit from more choice. And even if there were only one python and one ruby library for lets say XML-manipulation, it would be two more for perl. If the only reason for perl to exist were CPAN it should die. If not, there will be people changing from python or ruby to perl and not only in the other direction. One big advantage of open source is lots of users that find bugs, locate bugs and even fix bugs. I would not mind pythonistas finding or fixing my bugs.	[reply]