2 ms·
Again the maintainers solely responsible for that debacle are blaming others. It's perl6's fault, it's ruby's fault, it's javascript. Whilst they dont admit th
by rurban 6y ago
Again the maintainers solely responsible for that debacle are blaming others. It's perl6's fault, it's ruby's fault, it's javascript.
Whilst they dont admit they had nicely developed specs and list of features to implement (for perl6), but couldn't manage (technically) to implement even the most simple ones from 2002 to 2021.
Management is not-existing, developers all went elsewhere. You don't want to argue with people you have no idea. Famous is e.g. how Russ Cox was treated when re2 and backtracking DDOS was presented to p5p: https://perl.perl5.porters.narkive.com/guZUVhlv/article-on-perl-regexp-performance https://perl.perl5.porters.narkive.com/guZUVhlv/article-on-p...
Just a few amateurs and system admins, who use it for their job are dabbling with it and keep destroying the codebase. It was unmaintainable in 2002, and it's more so now. The language is fine, p5p (the development process) is totally broken.