comment on

Again I don't even understand what NFG is.

Our sub thread started here Re: Ovid's take on the renaming of "Perl6" and was about potential future optimisations.

You are concentrating in repeating what went wrong in the past and how promises were broken.

And it seems that I'm the surrogate target for your frustration.

Well if you need my confirmation that Perl6 is a classic example of bad management:

Granted!

Over optimistic
Osborning,
drivel heavy,
lost in community,
marketing desaster,
compatibility chaos,
etc.

But you've also been a poster boy of this management group for a decade, and I'm not targeting you with my frustration.

Let's end it here, ok?

I'd suggest you ask Ovid directly what he meant with his statement.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

PS: FWIW I asked Damian in Riga 8 years ago if P6 shouldn't better be renamed "Perl++" to reflect the compatibility issues. And he said probably yes, but it's "already too late."

In reply to Re^10: Ovid's take on the renaming of "Perl6" by LanX
in thread Ovid's take on the renaming of "Perl6" by 1nickt

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.


Problems? Is your data what you think it is?
	PerlMonks