News for hackers. Stuff that matters.
Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by wmf on Thursday May 27, 2010 @07:43PM (#1385252)
Why is the app 500MB? Because all the rich content are bundled into the app

The article says that rich content isn't the source of the bloat:

Each full page is a giant image – there are actually two images for each page: one for landscape and one for portrait mode.

If the app stored text as, you know, text then presumably it would require significantly less space. Eliminating the portrait/landscape duplication would also save space.

Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by wizard_2 on Thursday May 27, 2010 @09:44PM (#1385439)
The crazy layouts wired is somewhat famous for hardly translate to plain text with a few graphics. I don't know what they use to layout their magazine (or what they used 10 years ago!) but it's not html5. Translating, migrating, converting, or adapting their content to anything other then an image (except maybe PDF!?) would be extremely non trivial.
Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by JMiao on Thursday May 27, 2010 @10:50PM (#1385561)
article could be wrong. there's a lot of high-quality video in the app.
Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by DrSprout on Thursday May 27, 2010 @08:00PM (#1385283)
Perhaps I'm being overly cynical, but if their intent was to show what a load of nonsense Apple's insistence that native apps are better is, it sounds like they couldn't have done a better job.
Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by andybak on Thursday May 27, 2010 @08:09PM (#1385289)
Did you RTFA? You could have made this a native app using the webkit control and bundled all the content in a 10th of the size.
Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by DrSprout on Thursday May 27, 2010 @09:21PM (#1385413)
Yeah, I'm saying that from what I'm reading they must have intentionally been looking to create a completely native app that is worse than the Flash-compiled one.

That or the descriptions of the app are somewhat overcritical.

Re:500MB download? Why didn't Wired Magazine use HTML5 for t... by kevinelliott on Friday May 28, 2010 @08:49AM (#1386233)
To entertain your reasoning: Adobe certainly could have intentionally created a "sucky native app" to contrast their "awesome Adobe iPhone OS compiler" but they mostly left out features and released a bloated (size) app. If they truly made a native app with HTML-based text and image optimization, or use their compiler, they could have equally reduced the size of this app and increased the functionality beyond what they have done here. Thus, the current implementation does NOT do a good job of proving that their compiler could have been better than a native Objective-C app.

Even so, if Adobe did want to throw a laughing cog at Apple via their clients, they're doing Wired a disservice, and frankly, that's terribly insane. They just couldn't throw a high profile partner/client under the bridge just to amuse some tantric executive war between Adobe and Apple.

Lastly, although hard to believe a company fairly technology agnostic as Wired would use their financial line (their money making product) as a way to experiment with dissing a technology giant, let's pretend Wired and Adobe both wanted to stick it to Apple for the 3.1.3 clause. They would be simply shooting themselves in the foot, as their customer is who really loses out here, not Apple.

It just make any sense at all, although I will give you that it's a romantic idea. More likely, they rushed a replacement implementation, since they couldn't use Adobe's compiler. Conde Naste clearly upholds Wired to the same deadlines as their other high end properties, and want to see a ROI for all the R&D they've had, perhaps. Becausethis certainly looks like a rushed implementation, or at a minimum, one done by amateurs.