Live data from Hacker News

Web Developer Admits: Objective-C Beats HTML5

engblog.polyvore.com

11–20 of 26 posts

Re: Web Developer Admits: Objective-C Beats HTML5

#11

Beats it in how easy it is to create, yes. But HTML5 is cross platform, and if done properly, the speed differences are not noticeable to the human eye. In fact, "Fastbook" is proof that an HTML5 app can be FASTER than it's iOS counterpart. http://www.sencha.com/blog/the-making-of-fastbook-an-html5-l... Check out their video. They literally duplicated the iOS functionality, and made it faster, with HTML5.

Given the considerable resources that Facebook has, and the amount of effort they put into an HTML5 application at first, it seems reasonable that native still gives a much superior experience. Sencha has done some great things, but one must consider the bias Sencha has for HTML5 to be great. It is in Facebook's best interest to deliver the best experience possible, but it is in Sencha's interest to deliver promising…

> Given the considerable resources that ____ has ...

This is far from true. Example: Given the amount of resources Microsoft has and all the effort they put in UX it seems reasonable they have made the best UX decisions

No, that's provably not true.

It seems logical that the large resources of big companies would work that way but that's not how the real world works. It always comes down to just a few people and their taste. Rarely are these kinds of decisions made based on anything more than a few people's opinions whether it's Microsoft, Google, Apple or Facebook. Whoever is the lead programmer for a particular project or lead UX designer for another or one of the 2 or 3 people around them decide this stuff based on nothing more than their professional opinion. That opinion might be more informed than your average joe but it has nothing to do with the size of the company and their "considerable resources".

Re: Web Developer Admits: Objective-C Beats HTML5

#12

Beats it in how easy it is to create, yes. But HTML5 is cross platform, and if done properly, the speed differences are not noticeable to the human eye. In fact, "Fastbook" is proof that an HTML5 app can be FASTER than it's iOS counterpart. http://www.sencha.com/blog/the-making-of-fastbook-an-html5-l... Check out their video. They literally duplicated the iOS functionality, and made it faster, with HTML5.

> HTML5 done properly I've seen Gmail.app on a friend's iPhone 4S (with dual-core A5) and it's slower than Apple's Mail.app on my sister's iPhone 3G (with a 300MHz ARMv6, which I think is under clocked to 230MHz or something like that). When Google (king of the Internet and HTML5) fails to "do HTML5 properly", then the rest of us really don't have much chance. (and, no, it's not (entirely) UIWebView's fault. If Googl…

An email app like Mail just download and keep offline copies of most of the mail. Opening the app and it instantly shows the pre-downloaded stuff. Yes, so in that sense, the mail app is faster. Bravo.

The 40% faster boost takes us into the range of not-really-noticeable. If there were a dev tool to make efficient HTML5 apps just like there is to make native, and this speed difference was in miliseconds, not seconds, developers will flock to HTML5.

Re: Web Developer Admits: Objective-C Beats HTML5

#13

Beats it in how easy it is to create, yes. But HTML5 is cross platform, and if done properly, the speed differences are not noticeable to the human eye. In fact, "Fastbook" is proof that an HTML5 app can be FASTER than it's iOS counterpart. http://www.sencha.com/blog/the-making-of-fastbook-an-html5-l... Check out their video. They literally duplicated the iOS functionality, and made it faster, with HTML5.

They did not "literally duplicate the iOS functionality." After months of work, and modifying their own framework, they produced...a technology demo, which omits core functionality like searching. Also, I don't agree that the Fastbook app is HTML5 "done properly." From their article: So the Fastbook app is the first to make use of a brand new “Sandbox Container” which programmatically detaches complex views and rende…

No, of course they didn't duplicate every bit of Facebook's functionality. You missed the point, I'm afraid. The very specific functionality they targeted performed as well as the native app, and in some cases, better.

They are both pulling the same data from Facebook, and just displaying it to the user. One is native, one is HTML5.

Re: Web Developer Admits: Objective-C Beats HTML5

#14
post #8

Earlier quoted context omitted.

> HTML5 done properly I've seen Gmail.app on a friend's iPhone 4S (with dual-core A5) and it's slower than Apple's Mail.app on my sister's iPhone 3G (with a 300MHz ARMv6, which I think is under clocked to 230MHz or something like that). When Google (king of the Internet and HTML5) fails to "do HTML5 properly", then the rest of us really don't have much chance. (and, no, it's not (entirely) UIWebView's fault. If Googl…

I wasn't aware the gmail ios app is HTML5. Do you have some link that claims that it is?

It's a hybrid app. Native with some features implemented with web views.

http://geeks.everything.me/2012/12/09/451/

Re: Web Developer Admits: Objective-C Beats HTML5

#15

Earlier quoted context omitted.

Given the considerable resources that Facebook has, and the amount of effort they put into an HTML5 application at first, it seems reasonable that native still gives a much superior experience. Sencha has done some great things, but one must consider the bias Sencha has for HTML5 to be great. It is in Facebook's best interest to deliver the best experience possible, but it is in Sencha's interest to deliver promising…

> Given the considerable resources that ____ has ... This is far from true. Example: Given the amount of resources Microsoft has and all the effort they put in UX it seems reasonable they have made the best UX decisions No, that's provably not true. It seems logical that the large resources of big companies would work that way but that's not how the real world works. It always comes down to just a few people and thei…

Agreed. The resources Facebook put into HTML5 are irrelevant. 9 women can't have a baby in 1 month.

I think the biggest problem with HTML5 is development obstacles, and mobile browsers being under-powered.

Think of it this way: creating a fluid GUI can require AJAX, and a number of other tricks to streamline loading. But a native app can load the whole GUI at once instantly. To make a fast and responsive native app is hard NOT to do, while doing the same in HTML5 is HARD to do.

Re: Web Developer Admits: Objective-C Beats HTML5

#16

Earlier quoted context omitted.

> HTML5 done properly I've seen Gmail.app on a friend's iPhone 4S (with dual-core A5) and it's slower than Apple's Mail.app on my sister's iPhone 3G (with a 300MHz ARMv6, which I think is under clocked to 230MHz or something like that). When Google (king of the Internet and HTML5) fails to "do HTML5 properly", then the rest of us really don't have much chance. (and, no, it's not (entirely) UIWebView's fault. If Googl…

An email app like Mail just download and keep offline copies of most of the mail. Opening the app and it instantly shows the pre-downloaded stuff. Yes, so in that sense, the mail app is faster. Bravo. The 40% faster boost takes us into the range of not-really-noticeable. If there were a dev tool to make efficient HTML5 apps just like there is to make native, and this speed difference was in miliseconds, not seconds,…

I have to disagree. I didn't mean that Mail.app "shows stuff" faster because it's cached the data and there's no roundtrip to the server (BTW, Gmail.app does this too). I meant the animations, scrolling and general speed with which "things" happen after you touch something or swipe.

And as I said, even if HTML5 rendering gets 40% faster, it's still extremely slow compared to native UIKit stuff. HTML5 is like 3 times slower than UIKit if you have any animation (and by animation, I don't mean really fancy stuff even - even moving a rounded rectangle from point A to point B).

It's not this drastic on Android, but iOS's graphics stack has been heavily optimized so a lot of stuff happens in layers in GPU. UIWebView, because of its implementation, does (almost) all its renderings in CPU and almost by definition, is much, much slower than anything that's GPU-accelerated (and takes at least 50% more memory and power).

The difference is like night and day. Open Gmail.app in iPhone 4S or 5 (the new Gmail.app that was released a few weeks ago is faster than previous versions though), and open Mail.app in an iPhone 3G. You'll see the difference clearly.

Re: Web Developer Admits: Objective-C Beats HTML5

#17
post #14
post #8

Earlier quoted context omitted.

I wasn't aware the gmail ios app is HTML5. Do you have some link that claims that it is?

It's a hybrid app. Native with some features implemented with web views. http://geeks.everything.me/2012/12/09/451/

> Native with some features implemented with web views

Well, some is a little bit misleading. More like most (60-70%) :) - the old app was like 95% web-stuff. The new one (released a few weeks ago) does things more "natively"

Re: Web Developer Admits: Objective-C Beats HTML5

#18

Earlier quoted context omitted.

Given the considerable resources that Facebook has, and the amount of effort they put into an HTML5 application at first, it seems reasonable that native still gives a much superior experience. Sencha has done some great things, but one must consider the bias Sencha has for HTML5 to be great. It is in Facebook's best interest to deliver the best experience possible, but it is in Sencha's interest to deliver promising…

> Given the considerable resources that ____ has ... This is far from true. Example: Given the amount of resources Microsoft has and all the effort they put in UX it seems reasonable they have made the best UX decisions No, that's provably not true. It seems logical that the large resources of big companies would work that way but that's not how the real world works. It always comes down to just a few people and thei…

I do agree that it comes down to a few people and their personal taste, but I still contend that those few people are often some of the brightest in the industry.

That being said, the example such as Microsoft does ring true, and perhaps Facebook didn't give HTML5 a fair try. I still think that overall evidence has been pretty clear that native can still provide better performance.

Re: Web Developer Admits: Objective-C Beats HTML5

#20

Title should be renamed to "native code beats html5". I'd rather program in html5/js than obj-c anyday!

Its not really a question of what you'd prefer to code in (you'll always prefer something familiar) but what delivers the best result for what you're trying to do. In essence we created two real, not test, apps, one using HTML and one using Objective-C. The clear winner was Objective-C in our experience, at this time. Creating a great mobile interface using HTML5 is certainly worth doing and can be done - but I dont think it should be made to look and feel like an app (either in safari or wrapped) since the "not-quite-right" issues just keep piling up, and if you want the look and feel of iOS you should just go native in the first place.
Post reply on HN