4 ms·
> realize how sub par the [mobile web app] experience is why is this a given?
by chii 8y ago
> realize how sub par the [mobile web app] experience is
why is this a given?
- pjmlp 8y agoA proven experience since Symbian introduced the Web Runtime in 2011, with a few dead OSes pushing for a Web only experience?
- oblio 8y agoThere is such a thing as "good enough". The cheap plastic solution tends to win when that happens. We weren't there in 2011, maybe we're not there in 2018, but the writing's on the wall.
- pjmlp 8y agoWhen that happens, the browser would have turned into a general purpose VM running apps via WebAssembly with WebGL/WebGPU for rendering, thus becoming native as well. The writing is on the wall with the ongoing efforts on .NET, Java, Go, Unity, Unreal and who knows, someone might even port Flash to it.
- oblio 8y agoI don't consider an universal bytecode as native.
- pjmlp 8y agoSo according to you IBM and Unisys mainframes, the Xerox PARC computers, watchOS apps don't run native code.
- oblio 8y agoDo the CPUs of their respective systems directly understand the instructions? In my opinion, if they don't, that's not native code. Of course, for strategic reasons such as portability the manufacturer might not provide any kind of access. At which point that's the closest to "native" you're going to get...
- pjmlp 8y agoDepends, on the mainframes and watchOS, bytecode (or bitcode) is used as portable binary format and JIT compiled at installation time into native code. On Xerox PARC systems, the CPUs were micro-coded.