I think most of the complaints about moment are that it's really big (because of i18n and timezones). Obsidian isn't a web page/app, so it doesn't need to optimize bundle size too much.
The Gobi desert and the bottom of the ocean are far more hospitable for human colonization than anywhere off-planet (not to mention far, far cheaper and more energy-efficient)
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!
Use the debugger: `python -mpdb` is a very similar experience to `perl -d`, so much so that it feels like a gift from an earlier perl-to-python emigrant.
(I showed my co-workers `perl -d`, they later discovered and showed me `python -mpdb`)
You seem to be unfamiliar with the idea of a *personal web site*.
Hosted on one's own domain, hosting whatever content one chooses to throw up on a server, intended primarily for oneself and one's acquaintances, these things are as old as the web and among its most fascinating treasures.
My favorite Win32 tutorial is by Bartosz Milewski, I found it as a series of posts on his CodeCoop website (https://web.archive.org/web/20110129015721/http://www.codeco... ), that were later incorporated into his book "C++ in Action" (also findable online).
He uses C++ to wrap every resource acquisition in a constructor and every release of a resource in the corresponding destructor, so that by allocating new objects on the stack you avoid a whole swath of memory management errors. This was my first encounter with RAII (not sure if he calls it that), and it seems a particularly elegant way to write C++ and to make the raw Win32 C API a lot less scary.
The rough equivalents in the Perl ecosystem would be cpanm (for installing), carton (for managing project-specific dependencies), and perlbrew or plenv (which I think are more like pyenv than virtualenv)
Take it down another decade. Or two. There are versions of Old/Super/Hyper in libraries and frameworks for Java, Perl, Python... Once you get the Internet, the hype cycle keeps speeding up