As a SUSE employee myself, I want to add that it is also part of our company culture for employees to contribute code upstream whenever possible. That's how many of my own Open Source contributions happened in the past few years. Most recently building an MCP Perl SDK (https://github.com/mojolicious/mojo-mcp). SUSE is giving a lot more than just money to the Perl community.
The Minion job queue is another implementation of this idea. But using the even more efficient and safe FOR UPDATE SKIP LOCKED. https://github.com/mojolicious/minion
I've not really thought about that before, but looking through the commit history it actually seems very likely that we were the first. Back then the WebSocket protocol looked very different from today. https://github.com/mojolicious/mojo/commit/a1a7060e35a6a0965...
Thank you. I've been very fortunate to have found an employer that enables me to keep contributing to open source projects this actively. So SUSE also deserves a big thank you for making Mojolicious 8.0 possible! :)
Yes, Cpanel::JSON::XS can be configured to be closer to the original Mojo::JSON behaviour. And the maintainer has historically been more cooperative with efforts to make Perl JSON modules compatible with each other.
It took almost a year and multiple attempts to finally get rid of Perl 5.8, so glad it's done. :)
But thanks to Jesse and his ambitious plans for Perl, i think there is now a mentality change happening in the community that will make similar changes easier in the future.
In userland you actually don't have to install at all, there are no prerequisites to resolve and there is no build process.
Just unpack the tarball from http://latest.mojolicio.us and start playing. :)