Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^8: The current state of Perl 6

by Anonymous Monk
on Apr 20, 2010 at 04:46 UTC ( #835647=note: print w/ replies, xml ) Need Help??


in reply to Re^7: The current state of Perl 6
in thread The current state of Perl6

Well nobody is saying that the specification should be frozen such that it will be never changed ever after. What I meant was you must freeze it temporarily, match it, take feed back, modify as per feedback, freeze it ... and the cycle ... Every time you freeze it and the implementation that corresponds to it qualifies as a "Production Release" or "Spec complete" for that version of the specification.


Comment on Re^8: The current state of Perl 6
Re^9: The current state of Perl 6
by chromatic (Archbishop) on Apr 20, 2010 at 06:20 UTC

    Why bother freezing a specification you're going to modify anyway, especially given that almost all of the modifications in the Perl 6 specification in the past couple of years (if not longer) have come at the request of implementors?

    How is your proposal not a game of semantics dusted with a light sprinkling of unnecessary ceremony? Being able to point to any specific version of a specification won't change the fact that anyone remotely responsible and intelligent will have to evaluate any given release as to its actual qualities and not merely adherence to a specification that everyone knows will change from feedback anyway.

      All specifications have something called as a freeze point/Release/you-name-it eg : C++ 98 etc. And that is important because it gives the implementors and the users something to target to. If the C++ 98 specification was never frozen and would continue to evolve till todays date there would be no such thing called as a C++ implementation because the target itself is not complete and implementations keep going on... the bugs keep coming on... and ultimately the users get bored and just go away. As has happened in case of Perl 6.

      Take perl 5.12 for example, after two years of development a point was reached that ... Ok, here we are after two years lets stop here ... release this and carry on future development on top of it. There fore 5.12 is a production release and life goes on after that... Why can't perl 6 do that?
      As you yourself mentioned you are in the publishing business. Why do you have drafts and editions??? Why don't you just go on and on writing for decades making your novel/book thousands pages long without publishing it.

        To be fair, chromatic and others have been publishing what they call releases and what a publisher might call "drafts" of Perl 6 ("Rakudo") and Parrot for a long time, on a roughly monthly schedule already. It seems you're just uninformed and are trolling.

        ironically there are several obsolete Perl6 books published out there, which are of no use to anyone, so go figgure how much publishers care about the books the publish. (note:I am not a publisher, I'm just unhappy with this situation).
Re^9: The current state of Perl 6
by Anonymous Monk on Apr 20, 2010 at 06:38 UTC

    To freeze a spec, even temporarily, requires making a decision. But as soon as you set a goal, you create an expectation that it wil be met at some point.

    And the only firm decision taken on the various Perl6 projects, is to be indecisive. To manage expectations by creating none.

      To manage expectations by creating none
      they clearly haven't been able to manage that with Perl6...

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://835647]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (13)
As of 2014-09-19 20:52 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (146 votes), past polls