So that brings the choice to Winxed or NQP. Both are good choices,
though with different strengths and weaknesses. The issue of Winxed
not being included in the Parrot repo is not an issue. You could write
your code in winxed in a separate repo, and we could include a
"snapshot" of the generated PIR code in the repo. This is how we
distribute NQP, we take snapshots of the necessary files and
include them in the Parrot repo.
Eventually we might be able to do the same thing with Winxed itself,
and distribute a Winxed snapshot with Parrot. I can't speak for
NotFound on the issue, but he has suggested in the past he might be
willing to make a similar arrangement. If we have critical tools using
Winxed, that might help to inform our decisions in the future.
In the end you have to pick a language that you think you are most
comfortable with, and which you think is best for working in your
problem space. I can't answer those questions for you.
Good luck!
--Andrew Whitworth
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
>
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev