“Our biggest mistake was betting too much on HTML5″, sagte gestern der Gründer und CEO von Facebook Mark Zuckerbarg im TechCrunch-Interview. Es geht um die derzeitige Facebook-App für Smartphones. Die vorherige App, Benutzer werden diese Erfahrung gesammelt haben, lief langsam, stürtze oft ab. Dies hat mehrere Gründe, einer davon, sicherlich, ist HTML5, doch nicht nur.Der Hauptverantwortliche des HTML5-Standards, Michael Smith, sitzt mir gerade gegenüber, der zu diesem Thema folgendes zu sagen hat:
You know, the W3C is in this “HTML5″ thing for the long term. We are
building the foundations of the platform that’s going to last for a long
time — a platform for the future, for our children and our children’s
children, and further on, even. And looking at it from that perspective,
some of the features we are working on are nowhere near the level of
maturity that they’re going to reach over the long term. They are still
emerging technologies at this point, and for those of us who have been
working on making them a reality, it’s really exciting to be here at the
beginning of something that we know is going to have very long-lasting
impact on the world for a long time.
But at the point we’re at now, there are some challenges that you need to
deal with even when you’re using these emerging Web technologies in the
primary context in which they’re intended to be used — which is on the
Web. So it’s unsurprising to find that if they are taken out of that
context and used to do things like build native applications for mobile
devices, a few of them may not yet work quite as well in that context as
alternative mechanisms that are much more specifically intended for
building applications for those particular devices. That should almost go
Anyway, all that said, the technologies of the Open Web Platform are the
ones that are going to still be around long, long after most other
technologies for specific devices that currently happen to be widely used
have come and gone. The Web still be here when a lot of other things have
just become footnotes in history. (Remember WAP? J2ME?).
There are going to be plenty of bumps in the road along the way, but the
road ahead is clear. We’re not ignoring the deployment problems that come
up in the short term. Browser implementors are all working hard on
improving performance and have made massive strides in that area over the
probably on the order of 50 times faster than they were four years ago).
And we are actively examining ways to improve upon the initial versions of
some of the early technologies that have been deployed but for which the
deployment experience with them has shown that we still have some serious
problems yet to solve (e.g., the HTML5 “offline Web applications” feature).
All this is what naturally happens with developing standards for new
technologies: It’s in iterative process where we get the technologies
implemented and deployed, and then go back and continue to improve on them
based on the deployment experiences, until we have something that’s evolved
to be the best fit for what the real needs are.
So, about the news of some organizations building out native applications
for mobile devices using “HTML5″ technologies but then finding some
problems that limit the utility of those HTML5-based native mobile apps:
That really shouldn’t be seen as wholly negative news, because the fact
that they tried it all to begin with is a validation that the technologies
are far enough along in their lifecycle to possibly be viable alternatives
to purely native applications. That means these “HTML” technologies have in
a relatively short amount of time reached a surprisingly high level of
maturity. And in a little more time and you’ll be surprised again about how
much further they’ll gotten.