Apple's Flash policy is a breach of Postel's Law
scripting.com
scripting.com
Heck, I'll be generous and say that Dave might have a point if he were referring to an independent implementation of Flash, and what it ought do.
But mobile Safari is not a flash runtime, it's a web browser, and so its duty to the robustness principle is to be strict about what it sends (HTTP GETs and POSTs) and permissive about what it receives (HTTP responses, HTML/CSS/Javascript documents). It is no more obligated to include a Flash plugin than it is to have a plugin for Iterated Fractal Systems image compressor.
I think it's worth noting that there's an important class of software that needs to be strict about what they receive — compilers — and I often find myself wishing that browsers were more like compilers. But that's just when I get sour thinking about the excessive permissiveness of IE.
http://en.wikipedia.org/wiki/Postels_law
If anything, websites that depend upon Flash are "defective implementation that send non-conforming messages".
"Supporting plug-ins" is clearly a well-tested and marketed phrase to divert attention from the real issue: a business blockade. Only the weakest (or most biased) of programmers fall for it.
On what basis is a browser author obligated to support any plugin system whatsoever? I don't want an answer as to why Apple must...I want to know why any arbitrary browser vendor, in your world, should not be free to make that product decision.
Edit: I submit that if you cannot answer that question, having removed Apple from the equation, that it is not me who is biased.
It's not a lack of plugin support that prevents Flash from working on iOS. It's strictly business rules (which was the point of the article). Your first comment makes hay over the former and your second comment dismisses the latter.
* http://en.wikipedia.org/wiki/Strawman
"A straw man argument is an informal fallacy based on misrepresentation of an opponent's position. To "attack a straw man" is to create the illusion of having refuted a proposition by substituting a superficially similar yet weaker proposition (the "straw man"), and refuting it, without ever having actually refuted the original position."
Arguing that browsers should support plugins because they might be necessary to display useful information is a really slippery slope, and would be a wonderful way for Apple to get stuck in business relationships with notoriously incompetent companies like Adobe for little to no actual benefit. I'm not convinced that there are a significant number of people who would let the lack of Flash influence their decision to buy an iPad--certainly not a significant enough number of people for Apple to cede a portion of control over their platform to a company that has repeatedly demonstrated a complete inability to make Flash work on mobile (or really, any) platforms.
"... cede a portion of control over their platform ..." I can't help thinking that if Microsoft had restricted Quicktime from Windows machines, with the excuse that it's utter crap and no good, there would be an intense amount of lawsuits pending from Apple already.
BTW, Apple also does not implement Wordstar and WordPerfect readers, nor do they accept TARGA images. As much as I do wish 1) Adobe had a version of Flash that didn't suck; 2) Apple supported it, let's not attempt to invoke Jon's memory for this kind of stuff.
It's only asinine to pretend it's not a modern standard by reducing it to "just a plug-in" because it's unpopular (and virulently envied?) on this forum.
in your case: http://en.wikipedia.org/wiki/Slippery_slope
"A slippery slope argument states that a relatively small first step inevitably leads to a chain of related events culminating in some significant impact, much like an object given a small push over the edge of a slope sliding all the way to the bottom."
I am quite glad to be in a field where deductive logic is used; these sorts of tirades where its up for debate whether or not what you're saying applies (or was even correct in the first place) don't really happen.
I agree with you wholeheartedly, though. Calling everything a "law" is a nasty habit that has crept into compsci's pop literature over the last decade.
Well, MobileSafari doesn't have a plugin system available to third parties. Thus solving the issue: Postel's Law applies exactly nowhere in this case.
Other people might invoke Postel's name to amplify their own message, but that's just not what he was talking about.
Furthermore, if you believe for a second that Jon Postel would have been a supporter of Adobe Flash, then I assert that you weren't alive when he was. I imagine he'd have equally strong objections to Apple, but that's neither here nor there.
And I actually think it should (simply because that would be a convenience, if flash is to be replaced it can happen without resorting to user inconvenience as a means of applying pressure).
And this is not even considering that the iOS version of Safari (afaik) doesn't even have a plugin infrastructure to support 3d party plugins.
Personally I don't think Adobe can actually make a stable, efficient, full implementation of the flash plugin for a iphone/ipad style mobile device? After years of trying they still can't make one for any full power Mac, so why should anyone assume that they can for much slower mobile-devices?
I think Adobe's strategy is to make as much noise about the relevance of flash, keep promising an implementation of Flash "really soon now", while they'll wait until the hardware of mobile devices has become fast enough to handle flash without draining the battery.