News for hackers. Stuff that matters.
Re:Mojo.js is a port of Perl's Mojolicious to TypeScript by trinovantes on Friday November 18, 2022 @04:54PM (#33662901)
The first thing I consider when looking at Express-alternatives is if the API is fully compatible because almost every other 3rd party library/package (e.g. sentry) expects the Express object. This doesn't look like the case as I have no idea what the mojo context object is.

On a side note, I'm surprised to see frameworks trying to use benchmarks against Express as a key feature. Framework overhead is insignificant when requests delays are mostly due to the database/network.

Re:Mojo.js is a port of Perl's Mojolicious to TypeScript by christophilus on Friday November 18, 2022 @05:18PM (#33663211)
> Framework overhead is insignificant when requests delays are mostly due to the database/network

It really depends. When every part of your app is concerned with performance, it tends to hum along. When every part of your app tends to think, “the bottleneck is the database, so this doesn’t matter”, you get modern systems.

Re:Mojo.js is a port of Perl's Mojolicious to TypeScript by trinovantes on Friday November 18, 2022 @06:44PM (#33664615)
In the case of Express vs alternatives benchmarks, you're looking at differences in the sub 1ms range as these benchmarks simply test how much "hello world" you can return per second
Re:Mojo.js is a port of Perl's Mojolicious to TypeScript by kraihx on Friday November 18, 2022 @07:30PM (#33665144)
Express middleware support is on the planned feature list for 2.0 and beyond. Could also be implemented as a 3rd party plugin using the existing hook API though. https://github.com/mojolicious/mojo.js/issues/66