I've worked in Bioinformatics companies for over 20 years, so a big chunk of my programming career was working with Perl, and I've loved, used and advocated for Mojolicious since I first ran across it. It taught me about API design and testing, contributing to open source, and participating in a generous tech community. It also taught me about not being dissuaded from making the right technical decision by popular opinion or ego (for example, breaking with the consensus around PSGI/Plack interoperability to build the entire framework around async IO).
As the world around me and I moved on from Perl, I've experienced a sense of mourning and loss. I love Mojolicious but I realize I'll probably never again write more than a one-liner in Perl (certainly not on the job; the majority of my current employer's codebase is actually in R). Furthermore, it's become clear that modern web development belongs inescapably to Javascript (and maybe Typescript); In this light, the release of mojo.js feels like an act of love and consolation, a wonderful gift to myself and all other bereft Polyglot Perl expatriates like me.
I offer my love and thanks to the mojo core team - long may you rock on!
As the world around me and I moved on from Perl, I've experienced a sense of mourning and loss. I love Mojolicious but I realize I'll probably never again write more than a one-liner in Perl (certainly not on the job; the majority of my current employer's codebase is actually in R). Furthermore, it's become clear that modern web development belongs inescapably to Javascript (and maybe Typescript); In this light, the release of mojo.js feels like an act of love and consolation, a wonderful gift to myself and all other bereft Polyglot Perl expatriates like me.
I offer my love and thanks to the mojo core team - long may you rock on!