Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

chromatic talks a lot and babbles a lot and writes this huge pieces of stuff that are completely irrelevant and stupid.

me I'm a practical man, I don't like babbling, if I say I did something I'll show some code, I think the best articles are ones which try to keep a code/explanations ratio above 3/10 or 4/10 , but chromatic wants to take that down to something like 1/100 where his stuff is like reading some sort of novel ...

that's the big problem, software is not about writing stuff like that, it's about practical things, not "epistemiological" discussions. I mean nobody will read that, maybe some close friends of chromatic who enjoy debating the philosophy of the match stick, or the phisolophy of the philosphy lol.

I read his blog sometimes and I'm amazed when I see like 3-4 comments to a completely weird and lame article, I ask myself man... these people had nothin better to do than comment chromatic's article... such a waste

really.. it's just lame. and with all that lame stuff he's trying to put together a book. he's like saying "hey wanna buy my collection of useless stuff,cause I wanna sell it man and there better be some readers out there 'cause otherwise this stuff ain't gonna go well, and I need to get some stuff outta' my babblings ??"

I've read some books and I can surely say that his books are too verbose to be useful. Chromatic needs to write code in order to get material for a book. If he's writing lame code then there ain't no way in hell he's gonna gather up material fro a book. If you do lame stuff you can't expect to get teh awesomeness out of it, it's still going to be lame.

the problem is that the dude needs someone to tell him hey, you're lame, stop it, just stop it, it's enough. but he probably gets all this encouragement or just likes seeing his name on books

Chromatic and some other guys like him(guys that are so excited and make such a big fuss/hype about features that are taken for granted in many other languages) are the reason Perl is plummeting with an astounding speed and it will mark its end as a language, just becuase one guy, or better said a couple of guys decided to "revive" Perl by implementing stuff that's already here for lots of other languages and making a big fuss out of it. That's just lame

Perl needs to differ itself from other languages, you can't just come and say "Hey we can now iterate with 2 iterators over an array" and expect all programmers to be like "Wooohaaa man you're a god !!!" . What the f*** is that ?? Or "We just implemented OOP properly in Perl, how awesome is that !!!?!!? " and expect reactions like "Man, these guys are f*cking geniuses" I mean almost every language out there has this stuff already, Perl is not brining anything new.

I mean Perl is a nice language but with these lepers around like chromatic and some other guys that are pulling it very hard down to the very bottom.. it will soon disappear.

It's already extremely hard to have a community-driven language today. Heavy money must be invested in one and the Perl community surely does not have that, it needs to differ by something else.

In reply to Re^5: How to Implement Perl 6 in Ten Years by Anonymous Monk
in thread The current state of Perl6 by Anonymous Monk

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

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others romping around the Monastery: (10)
    As of 2018-06-25 15:00 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (127 votes). Check out past polls.