3 ms·
We seem to be heading for a future where the only application run locally is a web browser.
by skrebbel 14y ago
We seem to be heading for a future where the only application run locally is a web browser.
- TheLegace 14y agoYa I very much doubt that. It just looks more people who barely do anything productive are on the Internet just using Youtube and Netflix. While the people who are developing say something like Youtube(or god forbid something more useful and complicated) are left to fend for themselves, because hey what do they matter.
- tensor 14y agoWe seem to be making the same unrealistically broad generalizations over and over, never learning from our past.
- kryptiskt 14y agoWe seem to be heading for a future where every website says "Don't look at this, download our app!".
- Zigurd 14y agoThere are at least three reasons that won't happen: 1. Horses for courses: Once you get past superficial similarity, the Web isn't a universal application runtime. It is more appropriate for some kinds of apps, such as publication media, form-filling, etc. than others, such as apps with fine-grained interactivity, apps with significant endpoint computation, etc. 2. Nobody has cracked the "write once, test everywhere" curse of multiple implementations of a standard, never mind a standard as complex, and with such a long legacy tail as Web browsers. Web app frameworks still devote a lot of code to compatibility. "Native" also means "a single vendor's runtime." 3. Operating systems are different, and there are varying approaches to portability. Running in a universal runtime is one approach, and it has inherent compromises. For example, Microsoft has applications for editing Office documents for Windows, Mac OS X, and for Web browsers. Which one has limitations both in terms of integrating OS features and UI conventions, and it terms of functionality?