There are two issues here.
a) Using language in a consistent manner in Perl6 space
- the word 'specification' is used in Perl6 space both in the way it has
become acceptable in computer language design circles, but also in a new
and more nuanced way in Perl6.
- Perl6 is being developed using Larry Wall's 'whirlpool' model, as
opposed to the 'waterfall' model, and this has an impact on the use of
'specification'.
- The result of this double use is a sort of schizophrenia in Perl6's
documentation when it comes to defining itself.
- Possibly the schizophrenia is useful - a manifestion of junctions :)
b) Educating the world about Perl6
- There are several attempts to address this issue.
- The problems addressed by Parrot Raiser exist and are understood by
many of the developers.
- My guess is that it will be solved in multiple ways.
- We should remember that the way today's mature languages, such as
Perl5, C, Fortran etc are taught today has been developed over many years.
On 09/30/2013 10:39 PM, Parrot Raiser wrote:
This is related to the conversation on the Synopses, but its
sufficiently different that it probably justifies its own thread.
I want to start by making it clear that I'm not criticising the design
of Perl 6, or any of the people working so hard to make it great. I'm
just trying to address what I see as an obstacle to its adoption, (but
may smply be my personal limitations). I've been following the project
from the beginning, and have "Perl 6 and Parrot (2nd. ed)",
http://shop.oreilly.com/product/9780596007379.do which I understand
is no longer relevant.
<snip>
