> Does this fit into your requirements

Absolutely not. My requirements are simple:

• Come up with concise, clear language, assuring my code will keep running, and pledge that you will remain conservative.
• Stop fucking around with syntax. If someone (including you) wants a new way to express the same thing, but shorter, they should pay the XS tax, not my userbase.
• Implement primitives that people actually want: performance improvements (order of magnitude) and parallelism with shared memory.
• Do it before distributions (rightfully) stop carrying /usr/bin/perl by default.

Then maybe (and that is a huge maybe) I may reevaluate if something new is worth writing under /usr/bin/perl again. Today the answer is a resounding "fuck no".

P.S. Golang the language (syntax-wise) is almost as shitty, and in places way shittier than Perl. Syntax is sugar: I have no problem copy-pasting code like an animal, provided my programs works, can push the resources I have to the max, and will continue doing so for decades.

P.P.S. You really should not care what I think: I have not been paid to write perl since 2018, and I am unlikely to do so in the future. Perl work on a resume is a liability these days, unless you are happy with booking-level pay. I am decidedly not your target demographic.