But making a release is a lot of work.
We've seemed to manage it 24 months in a row for Parrot.
Much bikeshedding will go on. And noone will actually do it.
I ported a proof-of-concept of roles to Perl 5 several years ago, and I wrote the class patch for Perl 5 last week.
It would be nice if someone invented something easier, and implemented it. Actually, someone already did, and called in Inline. Again, who's going to do the work?
I backported Parrot's solution as a proof-of-concept for Perl 5, again several years ago.
What's the "need" for perl5?
CGI is dead-ish, and mod_perl isn't easy to configure or deploy, and it's a lot of overkill for a shared-hosting account. Somehow mod_php has managed to make thousands of PHP apps as easy to install as "Drop this file in a directory." Isn't ease of deployment important?
Nicholas Clark is fond of saying "perl development is driven by people who haven an itch". Which basically means "something is only going to be added/changed if someone is motivated enough to do the work".
How much more code do I have to write to earn the right to make suggestions?
In reply to Re^2: Five Features Perl 5 Needs Now
by chromatic
in thread Five Features Perl 5 Needs Now
by Arunbear
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |