There are more than a dozen of frameworks for developing Web applications. Why bother to have another?
The short answer is that they are either too limited to deliver the rich user experiences, or too complex and costly to develop a Web application. In 1994, we developed an infrastructure, inspired by zApp and OWL, for developing an accounting system for Windows. In 2000, we developed another infrastructure, inspired by Struct and WebWorks, for developing another accounting system for J2EE. After coaching and watching the development of both systems, we found that not only the Web edition required much higher programming skills and prerequisites, but also its total cost is four times more than the client/server one. Worse of all, the user experiences reminded us the age of green terminals, though the look, after decorating with proper images and CSS, is modern and fresh. We start wondering whether it is intrinsic, or the programming model is simply inadequate. Looking back the success of desktop applications in 1990s, the event-driven, component-based programming model played a big role
