For sure; especially with web sockets. The built-in test support for the latest websocket spec (in code and on the command line) makes things really easy.
If you thought that, Mojolicious will blow you away. The hot reloading production server and libev event subscription is about as hip as you can get these days.
I've been using Mojolicious even before it hit 1.0 and it has been an excellent experience. If there is one area I must applaud sri (and the community) for, is dropping Perl 5.8; Moving forward means moving forward (even though I understand the motivation behind not wanting to make 5.8 obsolete).
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.
A hard real-time operating system has less jitter than a soft real-time operating system. The chief design goal is not high throughput, but rather a guarantee of a soft or hard performance category. A RTOS that can usually or generally meet a deadline is a soft real-time OS, but if it can meet a deadline deterministically it is a hard real-time OS.
Async, non-blocking, and event-driven have nothing to do with real-time.
This web framework has nothing to do with real-time.
"The real-time web is a set of technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates."
I build a special-purpose frontend to libvirt using Mojolicious 1.33 back in May. It was already a very easy to use and capable framework. There have been 62 releases in the five months since then!
27 comments
[ 4.3 ms ] story [ 64.3 ms ] threadLast development release was on 20th Sept 2011 - http://www.nntp.perl.org/group/perl.perl5.porters/2011/09/ms...
If you're trying to get new blood linking to a site without docs, or any apparent links to get more info is maybe not the best way of doing so.
Specifically:
A hard real-time operating system has less jitter than a soft real-time operating system. The chief design goal is not high throughput, but rather a guarantee of a soft or hard performance category. A RTOS that can usually or generally meet a deadline is a soft real-time OS, but if it can meet a deadline deterministically it is a hard real-time OS.
Async, non-blocking, and event-driven have nothing to do with real-time.
This web framework has nothing to do with real-time.
Stop using terminology you don't understand.
As posted in http://en.wikipedia.org/wiki/Real-time_web
"The real-time web is a set of technologies and practices that enable users to receive information as soon as it is published by its authors, rather than requiring that they or their software check a source periodically for updates."
Mojolicious fits that description.
https://github.com/kraih/mojo/blob/7321e4c7b83a19286b3309df5...