I've found over the past decade or so that when I write a "perl" program I'm really writing about five lines of glue code around multiple CPAN packages. Well maybe more than 5 lines for control flow, some business-logic error handling, etc. When I write in another language I spend a long time looking for a library like the ten I'd find in CPAN, sometimes I find one but often enough not, then a long time complaining a…
CPAN might be centralized, but Java libraries are far superior. This is not a pissing contest, but a fact. The java runtime makes everything else look amateurish and unprepared. Debugging, profiling, introspection and distribution, all built into the platform. Attach to any running process and analyze away. Perl is good when it works, but when it doesn't, it's cryptic stack traces and `exit -1`, nothing meaningful.
Interesting. It never occurred to me to want this. What sort of use case is this for? It seems Perl is capable of something similar:
use Enbugger::OnError 'USR1';
Then 'kill -USR1 pid' and your process will jump into the debugger.learn more here: https://metacpan.org/module/JJORE/Enbugger-2.013/lib/Enbugge...