3 ms·

There will likely always be uses for the native platforms, especially on the desktop/power machines. I don't think React Native is targeting any of what you're

There will likely always be uses for the native platforms, especially on the desktop/power machines. I don't think React Native is targeting any of what you're talking about though. What the web has going for it (and what native will never catch up to) is having solved the distribution problem. Fact is, I can deploy to more machines, faster, and more securely than native (at least if there remain fragmented vendors) ever will be able to. I can already access most sensors and can run shaders. It's not like it's difficult to get what's missing into the browsers either and all the native vendors are also spending the resources to develop the browsers.

pjmlp 12y ago
> What the web has going for it (and what native will never catch up to) is having solved the distribution problem. apt-get, yum, app stores, click once, web start, ...
- jsprogrammer 12y ago
  Right: fragmented, environment dependent, user learning curve, etc. Web: URL + links
  - pjmlp 12y ago
    Web: Network always on required (offline apps is a joke), code behind a pay wall, data behind a pay wall, forced upgrades, removal of features without respect for the users, no guarantee of availability
    - arxii 12y ago
      >3 minute installer with possible malware >a url pick one
      - pjmlp 12y ago
        You forgot >a url with a JavaScript exploit >a url with a img/css browser buffer overrun >a url with cross site scripting I see no difference. EDIT: Actually I do. I is easier to exploit users that can't wait 3 minutes.