The shared storage redis backed option is great. I hacked together something that served .well-known from an NFS mount to overcome my issues when behind a proxy / LB.
My $work has a very terribe DNS infrastructure that needs lots of work to implement dns-01.
I have this requirement. I just bought a Toshiba Z30t. Ultrabook that is self serviceable and supports 16GB. But build quality and feel - talk about your pieces of shit.
Mojolicious for one doesn't have the dependency tree of Catalyst, this is kind of against of the Perl mantra of don't re-invent the wheel.
That said I favor Mojo over Catalyst for almost every project these days, it's very easy to work with and quick to prototype an application using the 'lite' mode.
Wow.... 15 years! Working at a hosting provider way back when I would die a little inside every time someone asked me to install phpmyadmin for their databases.
I'm sure it's come a long way (at least I hope it has).
Not surprising. Been through many MS -> OO and back again with various organisations throughout the years. OO is good if -everyone- uses OO.
In most organisations you get some genius who develops a fancy-smancy spreadsheet, visio diagram or word document with linked data which will be dependent on the MS access runtime, this gets distributed to all the OO users and it just doesn't work.
Take something you have coded in PHP and see how easy it is to re-factor in both languages.
There are no downsides to knowing all of these web frameworks, eventually you will find yourself in a position where company X only wants Ruby, or company Y only writes python.