Last check on 2001/9/16

Pliant is currently three things: a language, some applications and an operating system (see what is Pliant for extra details).
All three parts are now basically stable.
So, at the moment, if you plan to start a custom, mainly database, application, Pliant provides all you need to write the code and setup and maintain the servers and clients. Using Pliant will seriously bring down the overall cost because of Pliant's tight consistency.
Now that Pliant is both feature complete enough and stable enough for many real applications, I'm starting to do what I call 'polish' it (which means rewriting some small parts to get cleaner code, remove small bugs and design flaws, make it more flexible etc) and more than anything else, upgrade the documentation.
I also plan to publish a Pliant journal once a month that will demonstrate how to provide basic services using Pliant.
Finally, I need to switch to an even more open development model where, each night, I post two patches on the forum, one including the changes of the day, and one including all the changes since the last official release.

Pliant desktop applications (Word processor and spreadsheet) will use HTTP/HTML as their native user interface so that the documents can be viewed and edited from any web browser. They will also use HTML as their native file format so that the document can be viewed without the help of any server of specific application. The extensibility of HTML (the ability to add properties to tags) will be used to code application specific properties (such as the formulas in the spreadsheet).

First of all, we need a guy with reasonable programming capabilities to carry the day to day Win32 port (when I make changes, it sometimes breaks details in the Win32 port).