I admit to laugh, quite openly, when I read things (in the linked article) such as ... “there are things about regex culture that need breaking.” That is truly spoken like someone who doesn’t have a million lines of in-service legacy code to maintain. “Yee, hah, let’s go changing the fundamental meaning of the language to make it (according to me, and the rest of you are wrong) –er.” If you think I’m going to approve a budget-dime for that, or lobby for it to be approved, you’re nuts.
That’s why Perl-6 is still, stillborn. Because a programming language, really, is quite a small thing compared to the vast amount of in-service application and CPAN-library code that is out there. (The market value of which, I think, rests easily in the billions of dollars.) There is no evolutionary transition-plan here; not does one appear to be possible, let alone economical, let alone particularly beneficial. It would be very nice (may-be) if it were otherwise, but it isn’t. The syntax may be “ugly,” but there are by-now millions of examples of it in $$$ervice.
In reply to Re: Capturing parenthesis and grouping square brackets
in thread Capturing parenthesis and grouping square brackets by Eily