4 ms·
Some of this looks great. I'm suffering through making some internal tools an old version of php after deprecating some older perl 5 cgi scripts on an even olde
by scrame 11y ago
Some of this looks great. I'm suffering through making some internal tools an old version of php after deprecating some older perl 5 cgi scripts on an even older CentOS box, and reaaally not enjoying it.
I understand the value of coding in other texts, but I still get a little squicked out seeing the characters for pi, and union, etc in code. I know they have ascii equivalents, but its not saving a keystroke, exactly. Though, it does remind me of some joker Swift posts where the identifiers were all emoji's. I'd keep interns away from it for now.
The built-in grammar parser looks great! C-lib integration looks promising. Multi-methods look nice. Operator overloads look ... safe-ish-er than C++. Simpler profiling.
Perl5 module + other language in-lining looks great and terrible. "Whatever" wildcards don't quite seem like full pattern-matching, but better than $_ or endless shift loops.
Overall, seems pretty good!
If I can just drop it in for my "perl -lne 'm|($regex)|g&&print$1'" command-line use I might swap it out sooner than later.
- zoffix222 11y agoYou read a piece of code many more times than you write it, so even if an extra keystroke is needed to make the code more readable, it's worth it, IMO. But, I find it very easy to type all that fancy stuff with XCompose sequences. My keyboard also has a bunch of media keys I never use, so it's probably possible to map those into the unicode ops.