Quote:
Originally Posted by tomsem
... That says nothing about file size overhead for a real app, or runtime memory requirements or performance, which are arguably more critical and which the article leaves very much in question - but I'm not convinced that additional file size in and of itself is evidence that this approach is a dead end.
It's rare when a multi-platform toolset can outperform a native platform toolset (assuming best practices), nobody expects that it will. The question has always been (for Flash, Java, whatever) whether the performance tradeoffs are offset by the obvious, if sometimes elusive, benefits of 'write once, run many'.
It's all moot in this case since Apple has banned all such approaches, which is their right, and while it may not be to everyone's liking, they may well be making the best call for the success of their business (I'd like to see a credible argument that it is a bad business decision, if anyone has or knows of one). It remains to be seen.
|
Good points.
The only credible argument for it being a shortsighted decision is that if in a few years Android becomes the platform of choice (which it may, because of its openness both in terms of hardware and software), the iPhone may start losing developers. But who knows.
In any event, full Flash will be on all new Androids as of June. IMO, this was the real cause for both the vitriol and the timing of Jobs' letter.