zlacker

>>bertma+(OP)
I don't think Google has handled Android particularly well, but you have to be on some 1990s Netscape kool-aid to think that the web is or should be "the primary way for users to experience computing". Computing is just one kind of online service, and despite decades of effort to attempt to force-fit all applications into a browser, sometimes just a damn program that runs natively on the CPU is a much better fit for the task. Computing through the use of such programs is not a bad thing. Providing a central distribution point for such programs is not a bad thing—Linux distros do it all the time. Some of the fuckery-duckery Google has tried to pull with Android should be criticized, but it's not as cut and dry as "the web is open, everything else is proprietary vendor lock".

>>bitwiz+N2
> despite decades of effort to attempt to force-fit all applications into a browser, sometimes just a damn program that runs natively on the CPU is a much better fit for the task

WebAssembly will run natively if ECMAScript is holding you back.

While it's still on a VM, so is Java, and that's the only mainstream game in town for "native" Android apps.

It'd be exciting to see what the web could be if Apple didn't spend decades dragging their heels implementing standards for progressive web apps (PWAs) because they know it'll cut into their app store gravy train.