4 ms·
Having deployed Plack and Mojo in production, I would say Mojo's documentation is hard to digest. If you stray from a simple web-server with routes, you are re
by arbie 8y ago
Having deployed Plack and Mojo in production, I would say Mojo's documentation is hard to digest.
If you stray from a simple web-server with routes, you are relegated to reading Mojo source code to identify how to integrate esoteric middlewares (I'm looking at you, JSON-RPC 1.0 and Azure AD). Weirdly, it shares this "no help off the golden path" problem with Varnish Cache's VCL docs.
However, Mojo is still the most full-featured library out there, and you can easily bend it to your will. Hypnotoad is a process-based worker pooling engine for Mojo; its performance is not terrible and debugging issues is easy.
- SwellJoe 8y agoI found the Mojo docs to be better than most Perl frameworks, but Perl web frameworks, in general, suffer from a severe lack of good examples and docs. There's just not as many people using them as Node or Ruby or Python or PHP or whatever, so you don't find as many videos and tutorials and such for anything outside of the most basic stuff. I think there's also a bit of bias toward expertise; most people still using Perl have years of experience, and so there tends to be a lot less hand-holding, which is a problem if (like me) you haven't followed Perl web development closely, and only have a sort of old school understanding of it. There's quite a bit of "now draw the rest of the fucking owl", situations, for me, in dealing with modern Perl concepts. But, I like Mojo, nonetheless. It's really concise and does a heck of a lot with a vanishingly small amount of code (it's inspiring to see Perl excelling at something pretty modern, honestly).