Re:It’s cheaper to build multiple native applications than o...
by LnxPrgr3 on Thursday June 09, 2016 @04:58PM
(#11872337)
Not to mention the effect of time. The Web is not a stable application environment, and you may get caught in limbo, where the old way to do something is technically deprecated, but only one browser implements the new scheme, and only in nightly builds and even then only if you launch with --please-segfault-hourly. But using the deprecated API means at some arbitrary point in the future your working code will stop working.
Re:It’s cheaper to build multiple native applications than o...
by asadotzler on Thursday June 09, 2016 @06:28PM
(#11872852)
The Web rarely deprecates features. Browsers still have to display the Web of 1995.
Re:It’s cheaper to build multiple native applications than o...
by LnxPrgr3 on Thursday June 09, 2016 @07:21PM
(#11873131)
How about the Web of 2012?
WebSockets changed wire formats multiple times before we settled on something. Last I checked, the API still isn't final, and changes in browser behavior forced a project I was on to abandon it for socket.io. Web Audio has been through at least one breaking rewrite since 2012, and still isn't finalized.
Sure, '<h1>' still gets me a big, bold heading (probably, subject to CSS), but playing a sound file without plugins is still bleeding edge, and subject to arbitrary breakage. But we've broken plugins (for the best, eventually), so the old solution to that problem no longer reliably works.
Re:It’s cheaper to build multiple native applications than o...
by dragonwriter on Thursday June 09, 2016 @06:31PM
(#11872862)
> The Web rarely deprecates features.
No, it rarely removes deprecated features.
Beyond this, it is clear to me when an iOS-minded developer creates a web app that ends up on Android. Each have their own specific styles, and this gets lost with web apps.