Live data from Hacker News

Mojolicious 8.0 released: Perl real-time web framework

blog.kraih.com

21–30 of 35 posts

Re: Mojolicious 8.0 released: Perl real-time web framework

#22
post #6
post #3

What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.

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#...

Congrats on the release.

> mostly means WebSockets these days

And some WebRTC. Sub-100 ms latencies. 200? Voice and video chat, and gaming. npm's Primus. PubNub.

>> As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.

'Realtime web' has been a phrase for a decade-ish - used to be server push. Google is fruitful; the Wikipedia article... needs help.

Re: Mojolicious 8.0 released: Perl real-time web framework

#23
post #6
post #3

What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.

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#...

[deleted]

Re: Mojolicious 8.0 released: Perl real-time web framework

#24
post #3

What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.

Mojolicious was maybe the first framework with Websocket support.

Re: Mojolicious 8.0 released: Perl real-time web framework

#25
post #11

Just recently trying to get into Perl (trying to bone up for a specific position that requires it) and Mojolicious has been an incredible discovery: the "lightweight" Rails/Django replacement (somewhere between Rails and Sinatra in terms of ceremony and structure) I've always wanted.

Mojolicious is a mind-blowing framework, doubly so with Mojolicious::Plugin::OpenAPI. Unlike Catalyst, there's very few dependencies.

For a beginner, I'd recommend reading "Learning Perl" by Randal Schwartz first, then read a couple of the online Mojolicious tutorials/blogs.

Also, beginners should note that there's 2 framework approaches, Mojolicious::Lite (a wrapper) and the full Mojolicious, and mixing up the examples or documentation will confuse you.

Re: Mojolicious 8.0 released: Perl real-time web framework

#26
post #11

Just recently trying to get into Perl (trying to bone up for a specific position that requires it) and Mojolicious has been an incredible discovery: the "lightweight" Rails/Django replacement (somewhere between Rails and Sinatra in terms of ceremony and structure) I've always wanted.

Mojolicious is a mind-blowing framework, doubly so with Mojolicious::Plugin::OpenAPI. Unlike Catalyst, there's very few dependencies. For a beginner, I'd recommend reading "Learning Perl" by Randal Schwartz first, then read a couple of the online Mojolicious tutorials/blogs. Also, beginners should note that there's 2 framework approaches, Mojolicious::Lite (a wrapper) and the full Mojolicious, and mixing up the examp…

Yep I'm tearing through "Learning Perl" and "Intermediate Perl" (aka the "llama book" and "alpaca book") while also trying to do some "practical" projects in Mojolicious (https://github.com/ctindall/hotseat is the closest to an actual releasable project, which also has a client in Racket (which I'm just trying to get into, though just for fun)) to apply what I'm learning.

Re: Mojolicious 8.0 released: Perl real-time web framework

#27
post #24
post #3

What does "real-time" mean in terms of a web framework? As a web developer for over a decade, I don't recall seeing a web framework described with that before and have no idea how to interpret it.

Mojolicious was maybe the first framework with Websocket support.

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...

Re: Mojolicious 8.0 released: Perl real-time web framework

#28
post #9

Earlier quoted context omitted.

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.

>And the maintainer has historically been more cooperative with efforts to make Perl JSON modules compatible with each other. Indeed, MLEHMANN's (JSON::XS maintainer) difficult personality was one of the main reasons why Cpanel::JSON::XS was created and why it has gained so much popularity despite being almost identical functionally.

I would rather point out that JSON::XS simply refused to fix its most important bugs, and rather blamed upstream. I simply fixed those bugs and kept maintaining it. I also added many new features, just streaming support not yet.

The name is a bit unfortunate though as Cpanel itself still refuses to use it for political reasons. There is a high-profile jerk there running an agenda for his own personal profit. So I rather want to persuade Lehmann to give me his namespace and continue with it under the original name.

Re: Mojolicious 8.0 released: Perl real-time web framework

#29
post #27
post #24

Earlier quoted context omitted.

Mojolicious was maybe the first framework with Websocket support.

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...

Close, socket.io’s first release was on January 3rd 2010. There were a few other experiments before that in late 2009.
Post reply on HN