Ben Ward has written an excellent post about Cappuccino, the web application framework by 280 north that lets you "build desktop-caliber applications that run in a web browser". He expresses a commonly-held criticism of Cappuccino, which is that it divorces developers from having to understand or appreciate the core web technologies and principles of HTML, CSS, JavaScript, openness and standards. In doing so, it encourages people to create web apps that simply don't work well with the rest of the web, and simply ignore most of the last few years' significant progress in accessibility, interoperability and more across the rest of the standards-based web.

I generally agree with most of Ben's sentiments -- I am a web developer first, and my experience with native GUI app development and Flash/Flex development run a far second and third respectively. However, even after reading many similar rants, I still can't get myself angry about Cappuccino.

In my eyes, Cappuccino is an early, prototype of an open-source version of Flash/Flex, which is built on the standard web technologies of HTML, CSS and JavaScript. To me, this is a good thing to have around. There is increasing demand for desktop-style applications that are served over the web, and the idea of letting Adobe create another proprietary monopoly in this space scares me more than Cappuccino's backward steps.

Yes, its standards-compliance and accessibility are pretty dire at the moment, but I believe that these are things that can be improved. It's open-source, after all.