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

I don't mean to be overly rude but it seems it did matter that you wanted to speak Perl "baby talk" because you also wanted to readily understand everyone else's source (i.e., dialect). Your mentality perturbs me.

Perl 5 enabled you to baby talk blissfully. Perl 6 seems thoroughly poised to enable the same. How is that simple elegance diminished by the availability of optional advanced capabilities? I mean, were you lulled into some misguided silver-bullet idea because Perl has been so successful at making easy things easy that you presumed "baby talk" would also be sufficient to make hard things not only possible but easy too?!

If linguistic expressiveness && many solutions were the dark side of Perl that you were dismayed to discover, can the same be said about other programming or verbal languages you have endeavored to learn at least the rudiments of? I understand that time && effort to learn non-native languages are limited but does this justify taking a diminished outlook on a foreign language because you discover mind-boggling semantics in the poetry of the native speakers?

I don't think Perl 6 is trying to be all things to all people. Neither does it seem to be TIMTOWTDI gone wild (in any devastating, irrational, insurmountable, etc. way). Maybe you're just a joker && I should just laugh along instead of being potentially ridiculous by taking a serious posture against you but everything I've yet learned of both Perl 5 && 6 suggests that they'll both be awesome languages for quickly writing useful software (even if you only scratch the surface). It seems unjustifiable && unproductive to expect to readily comprehend average or expert composition without a commensurate expectation to proportionately expand your own relevantly featureless vocabulary && inadequate understanding of diction (&& then it's disingenuous to describe the distinction between baby && mind-boggling as merely dialectic).

Perl 6 may have a much higher complexity ceiling than any programming language that has come before but it's also progressing powerfully towards making easy things even easier && hard things easy now too! If you don't need to know more than one way to do something, you should be just as able to ignore the subtleties && the new semantics you are daunted by. If you ever find the time && inclination to learn more, hopefully it can be seen as benefit rather than burden to you... and hopefully you can also learn to harbor less resentment towards the fluency of adolescents, adults, && elders just as they concertedly foster your self-directed socialization process to be viably terminated during infancy. I don't know. I love Perl but I still know how very much I have yet to learn about 5. I'm just thinking it would be more helpful for everyone if you could think about your attitude a bit more carefully && maybe demonstrate more gratitude for ambitious progress rather than indignance, disappointment, && an immature sense of entitlement towards universal simplicity. Lowest-common-denominators don't lend well to improvement.

I'm convinced that Perl is greater than sliced bread... && sushi! ;)

Again, sorry if I'm being too harsh or flaming counter-productively or without warrant here. I just wanted to contest your quibbles with mine intelligently. I've still got lots to learn about being intelligent too! ;)



-Pip

In reply to Re^3: What's wrong with Perl 6? by PipTigger
in thread What's wrong with Perl 6? by duff

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 learning in the Monastery: (5)
As of 2024-04-19 17:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found