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

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
>> You are right no body really understands the complexity behind what you are trying to build. But ask yourself this question, How are they to understand when you haven't told it to them?

>IMO, this is more FUD ("Nobody is talking about Perl 6"). Here's an off-the-cuff and horribly incomplete list for 2009, in no particular order:

Sorry, but how many of these posts are talking about the complexity behind Perl 6?

I know some of the people and read a lot from them, I also read Dan Sugalski's blog from start till burnout.

I suppose most of these posts have the aim to keep people interested and get them involved and NOT to lower expectations or criticizing the complexity.

This is for sure a fantastic project, but we should start getting realistic about it.

The Perl community could have massive boost just by making a big release with "boring features"¹ but could then easily challenge the "sex appeal" from Ruby and Python.

Just like a plane is followed regularly by a bigger plane to keep the market interested and not by a rocket.

And I'm sure this major release would

a) put lots of pressure away from your team and

b) build a bridge to your project by incorporating concepts

c) therefore push the further development of it!

Cheers Rolf

¹) Nota bene: I don't say YOU are to implement these boring features!

In reply to Re^3: A wholly inadequate reply to an Anonymous Monk by LanX
in thread A wholly inadequate reply to an Anonymous Monk by pmichaud

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 or How to display code and escape characters are good places to start.
Log In?

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

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2021-07-28 18:03 GMT
Find Nodes?
    Voting Booth?

    No recent polls found