Front page | perl.perl5.porters |
Postings from June 2021
Reading discussion about RFCs, main concerns - up-to-date status is hard to track - rejected rfcs and/or parts are hard to track Tracking in mailing list still expects reading mailing list and remember every piece of discussion. Reasonably prepared RFCs (looks like I'm excluding myself already), even if rejected, should be preserved in rfc repository to prevent useless discussions. There should also be some written vision guidelines to prevent comments like "this is not perlish enough (because I don't understand it)" or long discussions about name of defer (when it was FINALLY). What perl wants to be? - just another but less popular java/python/... ? - referring discussion about trim What perl's target is? - make it easier to create code (20% of real life work, maybe even less) - or make it easier to maintain code (80%) What perl's values are? - language consistency? eg: "local sub" ... for experts local may be different from my, for average users they are same - developer experience? (part of it: I may be preparing RFC "introduce AST layer into perly => AST => OP chain" - when not feeling too demotivated)Thread Next