Re: How can HTML5 compete with Native?

> Opera Dragonfly was the first to offer remote debugging and proposed a
> unified protocol for debugging
> http://my.opera.com/dragonfly/blog/scope-protocol-specification
>

Very interesting stuff. Cheers.

A lot of movement is happening on the Chrome/DevTools side of things,
> though. Just the other day I came across
> https://developers.google.com/chrome-developer-tools/docs/debugging-clientsshowing different tools/IDEs/text editors integrating with DevTools (via
> https://twitter.com/ChromiumDev/status/392356326208069632).


Chrome also exposes the following API, which helps a lot with measuring
memory usage.
http://docs.webplatform.org/wiki/apis/timing/properties/memory

But all these APIs you mentioned need to comply to a standard to enable
third party tools.

On a more general note...maybe I'm just splitting semantic hairs here (and
> I'm known to do that), but perhaps the discussion should be reframed
> slightly. "How can HTML5 compete with Native?" is a loaded question,
> implying that Native has an advantage, that HTML5 needs to necessarily
> compete with Native, and that HTML5 needs to catch up with Native. Now, for
> some aspects, this may well be true...however, framing it this way could
> end up being quite limiting. Instead a more "What aspects of Native app
> platforms/development would be beneficial for the HTML5
> platform/development workflow" seems a less loaded approach (or maybe I'm
> just a hippy).


You are very much right. Thank you for pointing this out.

Dimitris Michalakos