Native Client in Chrome Beta
Nick Sabalausky
a at a.a
Fri Aug 19 22:52:04 PDT 2011
"Marco Leise" <Marco.Leise at gmx.de> wrote in message
news:op.v0f018nh9y6py2 at dslb-088-070-152-209.pools.arcor-ip.net...
>
>"By not adopting a technology capable of competing with native apps on
iOS, Android, Windows, and Mac, web vendors are preventing important
classes of applications such as high-end games and simulations from moving
to the open web."
That actually brings up an interestng point I hadn't really thought of
before:
I've always liked the idea of using native code instead of JS, because it
just makes so much more sense on a technical level. But, if something better
than JS, like NaCl, is adopted on the web, something that can compete with
real apps in efficiency, then that will only further encourage people to hop
onto Google's bullshit web-as-an-OS agenda. Even if NaCl is universally
adopted and completely eliminates the efficiency issues, the web will still
be horrid as a so-called "applicatins platform" for other reasons, like UI
(a big one), reliability, centralization, user-ownership, privacy... And
those issues aren't realistically fixable within the confines of a web
browser. So I think it's best if such a thing as NaCl *doesn't* get adopted,
since it would only further encourage the biggest plague of the 21st
century.
More information about the Digitalmars-d
mailing list