(2) is largely solved in mobile app development. We have everything from Dropbox to various data APIs. (1) is mostly a solved problem even on desktop, the web just got there first. No concern about the mostly broken Windows desktop: viruses, etc. App model: no broken installations of programs into desktop environments, dependency problems, DLL hell Data portability: log in from anywhere, have your data at your fingertips. I don't think anyone ever liked developing for the web. > As a broader concept, a return to prevailing use of on-device processing and computation (scroll down to see a bunch of examples) Today the too-facile argument that data must be shipped off-network to a third-party cloud in order to be processed efficiently means this happens all the time without users paying it any attention. * As a broader concept, a return to prevailing use of on-device processing and computation. Of course, back in the day, desktop apps were built in systems languages and not in JavaScript. Blisteringly fast on PCs of its era, a modern incarnation would seem incomprehensibly fast compared to today's bloated apps that have difficulty keeping up with keystrokes on 8-core 3.5 GHz monsters. I was especially fond of one named AK-Mail in the late 1990s and early 2000s. * High-performance lightweight desktop email clients. Combining its sprite model with the necessary several years of modernization it would have enjoyed had it not been abandoned would be impressive and easy to use. A little known sprite-oriented graphic arts program. Windows Phone was terrific in many ways and recent concepts by fans such as (Harry Dohyun Kim) show how beautiful the Metro design could be today. This week we are concerned about the loss of a browser engine, recognizing this is unhealthy for the market. We need a third viable option in the mobile space.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |