|I am looking for people who want to work on pliant with the goal of making it
a viable alternative for web development, that can compete
with .net, j2ee, ajax, cgi etc. development frameworks. The goal is to develop
websites, not web-applications, and to satisfy constraints of commercial sites -- ability to integrate
with existing websites. Some of the problems with current .page design is
- can't include .page output as an insert in a third party website
- can't recompile on the fly, so there are long delays between server restarts
and rapid prototyping of new features is difficult after the project is
broken up into .pli
- no framework for extreme programming / testing.
- need to easily define new meta (title, keywords) and header for every new page,
even if page is executed with execute_dynamic_page, or generated by a page
- need detect memory allocation errors or infinite recursion errors to
auto-restart the server so that the server is always up.
- need to update certain sections of the page, like the "section" mechanism
in the new ui design.
If all these problems are met, developing web-sites in pliant would be easy,
and one can start approaching small businesses (who may already have a websites)
and do web-programming to satisfy their needs. On the money made from these
projects, it is possible to advertise pliant to larger businesses, and to create
a job market for pliant.
Yes, it is possible to steal a market like this by providing a fast web development
tool. The proof for this is the way "ruby on rails" became popular.
No one was learning Ruby or cared about it until they created fast