4 ms·
I'm not limiting the web. You're not limiting the web. The web has limits. Actual, hard physical limitations (along with confidentiality and privacy limits); li
by EliRivers 11y ago
I'm not limiting the web. You're not limiting the web. The web has limits. Actual, hard physical limitations (along with confidentiality and privacy limits); limits that something running entirely locally, directly with your actual operating system simply suffers, and will always suffer, to a much, much, much lower degree. Your opinion (and my opinion) is meaningless when confronted with actual, physical reality.
Right tool for the job. That's all.
- netfire 11y agoBesides having to transfer data to run the application in the browser, what limitations are inherit in a web-based application? (I acknowledged the data transfer limitation in my previous comment). Browsers (especially mobile browsers) are unnecessarily limiting what can be done on the web. Adding additional permissions could enable browsers access to more system resources and components, especially on mobile. Could you provide some examples of applications that don't require a lot of data that couldn't be run in a web-based environment, because of physical (and not current browser or software) limitations?
- Navarr 11y agoDoesn't even necessarily have to transfer data with web workers, service workers, caching, etc. Google IO 2015, I believe, stores it's data so that when you load it up it loads from a cache that it's service worker will reload once you have it open. Allowing it to work offline and removing the cost of transfer at the beginning. I believe, not 100% on that.