Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Up front: I am not the right one for the job; I am largely recycling things I’ve read and heard. My experience domain in OO in other languages is sparse. So, I’ll rely on an expert!

I'd say the Moose OO model is far more powerful and useful than Python's. Roles, method modifiers, lazy builders, delegation and coercion are all really good for reducing repetitive code and improving OO design. With enough work most of that can be emulated in Python, but Moose gives it to you straight out of the box. Re: Python OO v Moose

Perl supports a vast ground of different techniques and does not hinder from crossbreeding or intermixing. Types + coercion for example, only hinted in the quote, can be bondage oriented or loose and accommodating or anything in between. You can write Perl that does what Java does in the way it does it (though private methods and such are less fun, you know they can be done in at least a couple ways; anonymous/lexical code and inside-out). You can’t do the reverse. Every personal sweet spot in between is possible in Perl. And though some languages—as I understand it, I’m *not* a xlang OO exert in the slightest—make some of the techniques easier and remove some of the bad behavior (like methods bumping into functions)… still Perl can do it.

Now to recycle another thing someone else said recently: The main problem with Perl isn’t Perl, it’s that while the CPAN is enormous, Perl at large is not grounded enough in complete, out of the box, applications. WordPress or Wikimedia would have been easy to write in Perl for example but the ethos of the Perl community, in my estimation, finds it more fun to work on gears than complete machines… I’ve thought a lot about this and I’ve never come to any conclusions; why, is it better, should, could it change? PHP only exists and flourished, in my view, not because Perl couldn’t do what it ended up being but because the Perl hackers of the day wouldn’t.

I ducked most of the real question, I know. It would be a good bit of work to address for someone who is an expert. It would be a three month research project for me. :P


In reply to Re^4: The future of Perl? by Your Mother
in thread The future of Perl? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (6)
As of 2024-04-25 09:59 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found