The web apps that will eat mobile

Re:The web apps that will eat mobile by pjmlp on Tuesday June 05, 2018 @11:24AM (#17238537)

When 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.

[ Parent | on HN ]

Re:The web apps that will eat mobile by oblio on Tuesday June 05, 2018 @11:46AM (#17238782)

I don't consider an universal bytecode as native.

[ Parent | on HN ]

Re:The web apps that will eat mobile by pjmlp on Tuesday June 05, 2018 @12:11PM (#17239079)

So according to you IBM and Unisys mainframes, the Xerox PARC computers, watchOS apps don't run native code.

[ Parent | on HN ]

Re:The web apps that will eat mobile by oblio on Tuesday June 05, 2018 @05:32PM (#17242288)

Do 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...

[ Parent | on HN ]

Re:The web apps that will eat mobile by pjmlp on Tuesday June 05, 2018 @06:21PM (#17242590)

Depends, 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.

[ Parent | on HN ]