That's where pyjamas, as an example, comes in: everything is abstracted. As issues are discovered, they are quickly patched to cover the anomaly, and off you go. This is a never-ending process: it's like cutting your grass, or weeding your garden. ("What does every garden need every day," goes the gardener's educational query. The answer? "Your shadow.") There doesn't have to be, and will never be (because of system complexity) a single answer. The solution is a systems solution: build in a framework that allows an easily acted upon corrective loop. Much like a gardener arranging the garden to allow easy weeding. <s>

Hank

>>>I've been reading this guy's stuff:
>http://cloudcomputingtopics.com/
>
>Sounds good- except that mobile internet isn't constant. Reading the newspaper on a device only is tolerable as the network cuts in and out because the page is cached locally. Database apps need local caches too. HTML5 actually comes with local cursors for this reason, but IMHO devices keep growing hardware features that customers reasonably expect apps to make use of without needing a rewrite. Fox tried to achieve this last century with UI metadata and pcode interpreted by runtimes for each machine. Not perfect, but a good model to make apps work on any device without having to write multiple custom versions. Whereas HTML does require custom coding and even extensions to make use of different hardware features and soon there will be proprietary HTML extensions and here we go again.