|I have been very pleased to read in this month release of Brave new
World the first serious article about Pliant. This one is not simply
copying one to two sentences from the documentation, and contains no
completely false assertion:
It makes me better understand that explaining Pliant is rather hard
because it's an overall vision about programming and computing rather
than a single product. So, many thanks to Georg C. F. Greve for his
One of the most important improvements that I expect in the next
monthes is a better definition about Pliant project goals as a all,
and how to achieve it (who works on what part, how do we select and
mixte various contributions, etc).
The start of this now central question will be the ASPIC on April the 3rd,
and it should be continued on the forum until this summer which is my
dead line for choosing a development model.
If you have suggestions about the way to best achive this goal
(producing a free, complete, consistent and flexible development system
including all basic applications), please talk.
I am very confident about Pliant language general design because I spend
15 years on it, and I think I'm good for that, but selecting a
development model, and turning Pliant from a single man project to
communauty of developpers that work nicely together is another story, and
I'm not that confident about my capabilities in this area, so preposals
(either through talks during the ASPIC or posts on the forum or emails
to me) are very welcome.
This is a critical moment in Pliant development process because many
of us have now understood that it has a real technical value, but it also
comes clear that it brings so much extra possibilities that it cannot be
handled nicely by a single man.