comment on

I'm curious if there's been any commentary from or interaction with some of the big Moose-y using projects (e.g. Mojolicious to name a specific instance) as far as what their plans would be / are.

Edit: Not that Mojo uses Moose in as such but it has its own maybe call it "Moose inspired" flavor.

Another: One of my worries (for lack of any better term) is that maybe at best it's an xkcd 927 situation and J Random Perlhaxor is now going to need to know how to do OOP TASK X / Y / Z in n+1 ways depending on the specific project/the ecosystem being used/the phase of moon.

(That being said these aren't really strong "worries" and it does look interesting at first (admittedly cursory) glance. I understand there may be whatever fundamental underlying implementation problems that won't go away without a re(design|write) and grant YET ANOTHER OOP SYSTEM may truely be the only way forward.)

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re: Cor—An object system for the Perl core by Fletch
in thread Cor—An object system for the Perl core by Ovid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks