Juerd wrote: > > It does make sense to have a single toolkit that does all this. It does > not make sense to have a single .pm that does all this. There's > absolutely no need for having all these different tasks in one module. > There's not even any benefit. You can just as well use a couple of > nicely named, grouped, and reasonably standalone roles or classes, and > then a single module to combine them all for the ease of use that you > like.
I suggest that those who have concrete ideas sketch out the API through a new page on the wiki. That could make it easier for someone else to pick up, if they have programming skill, but less API design experience. The result might be even multiple API designs (A more compatible CGI.pm and cleaner/newer/different Web.pm solution). http://rakudo.org/perl6/index.cgi Mark
