| |||||||||||||
Platform specific "apps" vs. HTML-based "apps"?Platform specific "apps" vs. HTML-based "apps"?Posted Dec 20, 2012 6:22 UTC (Thu) by jengelh (subscriber, #33263)In reply to: Platform specific "apps" vs. HTML-based "apps"? by dowdle Parent article: A simulated FirefoxOS experience
>Whatever happened in the war to make everything a web-application? Are browsers on mobile devices so sub-standard they don't fully support what we loosely call HTML5? The future was supposed to be web-applications...
Perhaps HTTP and its "lack" of certain "features" like server-side push and "full-duplex semantics" also factor in towards the decision to make a native app that tries to remedy that by using some non-standard side channel that a regular browser would choke on.
(Log in to post comments)
Platform specific "apps" vs. HTML-based "apps"? Posted Dec 20, 2012 7:59 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link]
> Perhaps HTTP and its "lack" of certain "features" like server-side push and "full-duplex semantics"
Both are easily emulated with long-polling. Which in reality is often better than simple TCP...
Platform specific "apps" vs. HTML-based "apps"? Posted Dec 20, 2012 9:12 UTC (Thu) by man_ls (guest, #15091) [Link] Perhaps HTTP and its "lack" of certain "features" like server-side push and "full-duplex semantics" [...]Now we have websockets, invented specifically to remedy those flaws. They work beautifully.
|
|||||||||||||