Corinna VS mojo

this the repository of initial draft:https://github.com/Ovid/Cor

after they proposed this, people debating around this in long time.

Have you been following the developments with Perl's forthcoming OOP engine, Corinna?

You can read about some of the discussions here (that's after the BUILD/BUILDARGS debate). Unfortunately, since much of the discussion took place on IRC, and there's a policy against allowing public logging without explicit permission of the channel owners (I am not an IRC guy, so I'm not one of the channel owners), much of this valuable discussion has been lost to time. I don't wish to repeat this mistake in future projects, but I can't change the past.

I've opened a discussion about revisiting Twigils.

However, I wouldn't shelve your plans to put more time into Moose. The PR for the initial Corinna work is out and while /u/leonerduk's work is great, the PR is huge and there are a few minor issues to deal with. I do not know when the initial Corinna work will be finished and even after that, it will be a couple of years before it's considered "stable."

From the Rationale for Corinna:

It's based on years of experience being the lead designer of the Corinna project and trying to figure out how we can get a version of Moose which is safer and easier to use, including removing a lot of boilerplate. This code:

By now most of you have probably heard about the Corinna project to get modern object-oriented programming in the Perl core. The RFC has been submitted to P5P and it's a slimmed down version of the full specification. It's in seven stages, each building on the last.

Then you'll be happy to know that I've submitted an RFC to the core Perl team to introduce a modern OO model to the language. So far the response has been positive and we already have /u/leonerduk who's committed himself to implement it.

Initial thoughts

If you end up doing web development, check out Mojolicious:

https://mojolicious.org/

If you choose to go down the Mojolicious road, there's lots of deployment information and guides in the Mojolicious Cookbook.

I guess this will make it harder to search for Mojo(licious)-related stuff. 😩

But if I want the return value of 'test_p' or the error message 'This is an error', I can't seem to figure that out. I tried looking at the promise tests (https://github.com/mojolicious/mojo/blob/main/t/mojo/promise.t) but that didn't seem to work either.

Several! The 3 big players in order of release are Catalyst, (released in 2005), Dancer2 (Dancer was first released in 2009, but went through a complete re-write as Dancer2 around 2013), and Mojolicious (released in 2010).

This project sounds to me like the perfect excuse to learn Mojolicious if you're interested in converting your scripts into a web application using Perl.

Awesome! I still use Perl on a pretty regular basis both for work and fun. I really enjoy it. Definitely take a look at Mojolicious if you haven't already. It's primarily focused on being a web framework (both server and client), but it's nicely modular so you can use bits and pieces of the stack. In i3mojo, I used the Mojo::IOLoop event loop, Mojo::Base as a base class system, and Mojo::UserAgent as a web client for some plugins.

Last time I used Perl for anything web it was via https://mojolicious.org/

It even does event-based and websockets