"With web-based software, most users won't have to think about anything except the applications they use.
All the messy, changing stuff will be sitting on a server somewhere,
maintained by the kind of people who are good at that kind of thing...
Desktop software forces users to become system administrators.
Web-based software forces programmers to. There is less stress in
total, but more for the programmers..."
Unfortunately the state of web-based application development is rather sorry today. It is not as easy as simple native program development - inspite of all the MVC models, devel environments (such as Struts), and so on. There are simply so many mistakes one can make.
And, if ASP is the way to go, then what could enable rather a large scale offering of web-based applications for end users? A simple deployment environment from a big vendor such as yahoo or google. (Let us call them "deployment vendor"). Such an environment would
And perhaps there are many other points. While most of these are usual ASP requirements, the enhancements because the vendor like google or yahoo have abundance of computing power, and can effectively create application development models around their infrastructure, is a different twist to traditional ASP.
And hopefully, these enhancements expressly incorporate principles of The web way.
Jotspot demonstrates this nicely, but it seems to hide the actual table data - perhaps storing it in a external datastore associated with the topic. But it is nice to store the table information in topic itself. (Bulk editing, no problems in renaming ...)
But unfortunately there is no standardized syntax for table within a wiki topic (of course we don't have any standard as of now). Wikipedia is evolving to be a great centralized resource, so might propel a standard creation process.
In this context, a useful link is discussion on table syntax:
Help:Table - From Meta; discussion about Wikimedia projects. In particular, even using XHTML as table syntax would help a lot: It might allow someone to create a nice table editing tool - with plugin approach to add semantics such as Spreadsheet ...
Neuro-aesthetics, Perceptual Grammar, Art, and Usability by Suman Kumar, wherein he connects usability to the fact that humans would like to minimize the work by brain (and supported by another study in this area).
And perhaps in many other areas (such as Adam Bosworth's emphasis on simiplicity in user interfaces, APIs etc.) - the same theme repeats. And yet, when we design things, we don't give sufficient importance to the simplicity angle - especially when you consider the cost of thinking involved in using and interacting with systems.
And perhaps the same principle is source of the bad designs in the first place!