7 ms·
The context wasn't really necessary. I think we all believe HTML5 has a great future. Hardware gets better at a rapid rate and HTML5 (CSS, Javascript, etc) is
by melling 14y ago
The context wasn't really necessary. I think we all believe HTML5 has a great future. Hardware gets better at a rapid rate and HTML5 (CSS, Javascript, etc) is still improving. The point is, and was, that it's probably best to produce native apps at this time, for the majority of apps. Facebook, for example, needs a 5 star app.
- muppetman 14y agoI think it adds the clarity that they don't think HTML5 is actually bad, but rather that it's still not ready for prime time (for them!) The many other quotes I've read around the web don't mention this, giving more of a "HTML5 sucks" hint to the quote.
- elorant 14y agoEven when HTML5 will be ready for prime time it could never compare to a native app. This isn't a new issue, cross-platform solutions have been around for ages and they always fell short.
- HyprMusic 14y agoSure, if you're comparing like-for-like experience and performance. But HTML5 provides advantages with rapid development, cross platform, distribution etc. over native apps. The debate is whether these advantages are enough to sacrifice the quality of experience and performance provided by a native app (or rather, whether the gap is sufficiently small enough to justify going for HTML5). Zuckerburg's opinion appears to be... yes, but not quite yet.
- MatthewPhillips 14y agoFell short in what way? Yahoo Mail came out in 1997 and people flocked to use it. You can guess what the UI was like for Yahoo Mail in 1997. But UX isn't only about UI. Being able to shop for a new computer or phone and knowing the stuff I use will continue to work is great UX as well. There are always tradeoffs. I'm tired of the anti-web brigade acting like web development is only good for the developer.
- elorant 14y agoOnce upon a time I worked at a company where we developed in a platform called Clipper. We used a cross-compiler to port apps from a PC to an HP-UX system. Although Clipper was based on C and the cross-compiler created C code it was never as optimized as it could be if written from scratch-actually it wasn't even close. In the years since I've heard numerous stories of similar situations. The one size fits all, which was best materialized by Java, never lived up to its name. You say HTML5 could deliver a unified UX. I disagree. If the problem is the need for unified visual environments then HTML5 is the wrong answer to this problem - CSS is more close to the answer. HTML5 was supposed to be that kick-ass solution for delivering a more robust development platform for the web that could reduce the need for third-party plugins like Flash or Silverlight. I won't argue that what HTML5 has achieved is no small step. But I wouldn't have high hopes of it ever manage to compare head-to-head with a native app, no matter how mature it would become-and that last part takes a lot of argument since evolution of HTML takes ages.
- MatthewPhillips 14y ago> You say HTML5 could deliver a unified UX. I disagree. Me too, I never said that. I said that, using Yahoo Mail as an example, users are willing to sacrifice some integrational purity when ease-of-use and portability are so compelling. Today that balance hasn't been tipped on mobile. I'm willing to bet it will be, eventually.
- indiecore 14y ago"HTML5" includes CSS, javascript and the actual HTML markup along with a myriad of other things.
- MatthewPhillips 14y ago> Facebook, for example, needs a 5 star app. Could you explain why?
- kirillklimuk 14y agoProbably the main reason that they have so much traffic going to the mobile website (aside from international audiences with dumbphones) is that the app sucks. My colleagues use the webapp on their androids because they hate the native app.
- moystard 14y agoFacebook relies on people using their service all the time, when they want. They want it to simply work. That's why they have this obsession about 24/7/365.25 uptime on their servers. It means also no friction when people use Facebook on their mobile, thus a 5 star app.
- veyron 14y agoThey have cemented their position. They can, at this stage, suffer down time without too much concern (hell, even twitter was down recently)
- adgar 14y ago> hell, even twitter was down recently You seem to think Twitter has a strong reliability record.
- army 14y agoFail whale...
- JumpCrisscross 14y agoI hypothesise user engagement would suffer in the face of down time. This, plus the added scrutiny this technical failure would place on their stock, means now is not a time when they can be careless about reliability.
- bad_user 14y agoNot necessarily a majority of apps. Facebook is a really, really popular app. They cannot get away with good effort alone. They must make their mobile app flawless and reliable, because if only a couple of users out of hundreds of millions publicly criticize their app, this hurts their reputation badly. I do not agree with what most people are saying. HTML5, CSS, Javascript are already good enough standards for 99% of all apps. The real problem lies with the popular mobile browsers. Anybody who ever tried developing a rich interface for Mobile Safari and for Android knows just how bad things are - and some people think having to support IExplorer 6 was painful. Also, at least on iOS, the browser has better performance than a WebUI embedded in an app. From what I know the web component doesn't use the same Javascript engine for instance. Also, not sure if this changed, but on iOS 4 you couldn't upload files from the mobile browser (file fields in forms were deactivated). You also couldn't automatically place the focus on a form field, to force the keyboard to pop, because you couldn't trigger any mouse/keyboard event other than in response to a physical user action (I think this was a problem with mobile WebKit in general). And I also experienced many problems with Android's browser. I can't even remember all of them.
- loumf 14y agoThe difference is that iOS allows Mobile Safari to turn memory areas into code pages, which is what you need to do to JIT JavaScript. It doesn't trust other apps not to be able to exploit that somehow, so UIWebView is not allowed to do this.
- rimantas 14y agoI'd say it depends more on app type than on HTML5 progress. For apps what are little more than glorified content viewers HTML is promising, for others — not so much. HTML5 brings some sanity and improvements, but at the roots it is still same old and lame HTML. You may spin and twist it, but at the end the question is "was it worth is". And the answer, most often than not is "hardly". Improving hardware won't change that, at least not substantially.
- ArekDymalski 14y agoWithout context this partial quote makes deceptive buzz in general media and that's gonna hurt many people and businesses.
- mbesto 14y ago> Hardware gets better at a rapid rate and HTML5 (CSS, Javascript, etc) is still improving. Hardware is only improving as fast the vendors see a need to. If the ARM chips in a smartphone suffice for say 90% of the games produce on a iPhone, why on earth increase it's power? We all know (hopefully by now) that the HTML5 spec chews through CPU, especially when called in parallel requests. It's not advantageous for Apple to optimize the HTML5 spec, otherwise it decreases lock-in. Also, this is the same argument that happened in the 90's with desktop/laptops and only really has progressed now with the existence of modern browsers. The only way that this was possible was when telecommunication infrastructure was able to support always connected devices, which the late 90's and early 2000's has proven. We are almost there, but considering 3G (4G, LTE, or whatever) is still not 100% reliable, I don't see this happening anytime soon. I really think we are less "connected" (technologically speaking) than the general public gives us credit for.
- seanalltogether 14y agoAlso core count is increasing, but raw speed per core really isn't. Multicore really doesn't help web rendering very much. Nearly all javascript out there is single threaded and most dom rendering is too.
- VMG 14y ago> Nearly all javascript out there is single threaded and most dom rendering is too. http://en.wikipedia.org/wiki/Web_worker http://en.wikipedia.org/wiki/Web_worker
- gliese1337 14y agoThat's really not a rebuttal. Yes, lots of browsers now support web workers. Yes, it is therefore possible to write multithreaded javascript. And that may become more common over time. But for now, the fact that it's possible does not change the fact that nearly all javascript is still single threaded.
- 14y ago
- NinjaWarrior 14y ago> I think we all believe HTML5 has a great future. I don't. Absolutely not. I have a confidence HTML5 will fail in the end. > Hardware gets better at a rapid rate Moore's Law is about to over. We have no free lunch anymore. The next Intel CPU (Haswell) gets only 10% performance improvement at the same clock. And don't you hear our consumers complaining the battery life and the heat problem of their mobile devices? Things become worse on the coming wearable computers. I can't understand why HTML/CSS/JavaScript advocates are so optimistic about this point. And looks like people completely forgot the buzzword of a decade ago, "green computing". My simple question is, "Are you really a SOFTWARE engineer?" HARDWARE engineers will solve the problem. Hah! > HTML5 (CSS, Javascript, etc) is still improving. Yeah, at a deadly slow speed. There are many critical bugs which has been stuck for several years. I'm tired to wait them fixed. Apparently web standards became too complex and about to collapse. Many programmers completely forgot the KISS principle. Very sad.
- Pkeod 14y ago> I have a confidence HTML5 will fail in the end. When is the end? What will replace it in the browser? Will people stop using browsers? Why do you have confidence other than things are not perfect now? >optimistic Being optimistic makes people want to solve problems. Being pessimistic makes people think defeat is 100% likely so they never try to solve anything. Our games already work very well in HTML5. They "work" on an iPad 3, but we still make native versions because the technology we use, Monkey, allows us to very painlessly do so. On desktop, Chrome, Firefox, and IE all run the games perfectly on a now 4 year old computer build. I'm not betting everything on HTML5 but to me it already is succeeding and I am confident that consumers will drive demand for it, vendors will produce and release devices which support it. Even if Apple, or the other big sellers don't support it there will be those who do and the great support will sell units and make anyone who doesn't support it well look bad.
- soup10 14y agoI believe you will always be able to make html5 apps if you want. But I believe the iOS 'apps' model is going to become the standard for consumer pc's. This will cause native apps to no longer be second class citizens, and HTML based apps will have to compete with native just like they do on iOS. Right now basically all consumer computing happens through the browser, except for ms office, and it takes enormous effort to get a non-technical user to install software.
- jksmith 14y agoInterestingly, once html5 becomes fully ubiquitous, Facebook will probably already be sliding no matter how well it's native apps run. Will be a non-issue in the end.