kraih
Joined 16 years ago
Karma
538
Submissions
56
Member since
Apr 19
Open Source Developer. Founder of Catalyst, Mojolicious and mojo.js web frameworks.
View on Hacker NewsRecent submissions
Comment · 1 year ago
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.
Comment · 4 years ago
mojo.js vs Mojolicious: 15x faster.
mojo.js vs Express: 3x faster.
Comment · 7 years ago
The new B&W PX7 actually has much improved ANC and is getting very close to the QC35.
Comment · 7 years ago
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
Comment · 8 years ago
Public release is what counts though, we had been privately experimenting with WebSockets for weeks at that point as well.
Comment · 8 years ago
The initial commit for socket.io was actually on March 17 2010. https://github.com/socketio/socket.io/commit/c8edad861a1b920...
Comment · 8 years ago
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...
Comment · 8 years ago
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! :)
Comment · 8 years ago
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.
Comment · 8 years ago
It's "real-time web", which mostly means WebSockets these days. (https://en.wikipedia.org/wiki/Real-time_web) But in the case of Mojolicious it is also used to highlight certain optimizations that make it very easy to use WebSockets and HTTP side by side in the same web application. https://mojolicious.org/perldoc/Mojolicious/Guides/Cookbook#...