So here's a question ...
Is it now, or should it soon be, reasonable to treat NQP as its own entity that
is a build target for a programming language, instead of treating Parrot as a
build target?
After getting the reference implementation of my language working over Perl 5
(because it is mature and well known to me), I had for awhile been planning to
use Parrot as the next major implementation target, by way of NQP, but it is
seeming now that it would be best for me to simply target NQP in its own right,
and then I would get something that runs on whatever NQP runs on at the time,
which might be more mature on the JVM or a non-Parrot backend for all I know.
-- Darren Duncan
