5 ms·
I understand your frustration, but I think you're complaining that you didn't get an option that was never realistically on the table in the first place. Your r
by Silhouette 12y ago
I understand your frustration, but I think you're complaining that you didn't get an option that was never realistically on the table in the first place. Your respect for the W3C matters a lot less to them than millions of people being able to watch content produced by a billion dollar industry, which much of that industry simply isn't willing to make available without DRM-style safeguards at the present time.
Yes, we used to use plug-ins for video. This worked reasonably well for quite a long time. I do think calling those plug-ins non-standard is a bit of a joke, given that Flash had 90+% market penetration for years and ran acceptably well almost everywhere, putting it far ahead of any browser in terms of portability and compatibility. By any reasonable definition, it was the de facto standard for on-line video streaming.
Then Apple decided not to follow that standard and broke the Web for their users. For those users, a lot of major sites still "don't work properly" today because of Apple's arrogance. Browser makers are playing along anyway, so now we have an HTML5 video ecosystem where the closest thing to a universally supported video format is patent-encumbered anyway. It is still supported on fewer systems than video using Flash players used to be. And instead of security flaws with your "non-standard" plug-ins like Flash, you're inevitably going to see security flaws with whatever media extensions you install instead (unless you think low-level, natively executed code written in error-prone programming languages and provided by the same kinds of organisations who used to provide the plug-ins is somehow magically going to be secure this time around, in which case I know a Nigerian prince who has a great deal to offer you).
This isn't progress. In what is becoming a serious and recurring problem with the modern web, issues other than what gives the best experience to users and makes things easiest for content providers to provide content are dominating the discussions. Many of the proposals are advocated by other parties with vested interests. And in the end, the result is that less stuff works, and stuff works less well, than the "legacy", "insecure" standards that have actually done the required job pretty well for a decade or two.
- TazeTSchnitzel 12y ago> I do think calling those plug-ins non-standard is a bit of a joke, given that Flash had 90+% market penetration for years Flash was also proprietary. It's closed-source, patent-encumbered, and has a single implementation. It's completely under the control of Adobe. https://en.wikipedia.org/wiki/Open_standard https://en.wikipedia.org/wiki/Open_standard > For those users, a lot of major sites still "don't work properly" today because of Apple's arrogance. As Apple explained countless times, it is not because of "arrogance" that they did not support Flash. Adobe weren't able to supply them with a working mobile Flash runtime, and Flash's resource use was a big problem (memory, CPU, battery life), so it couldn't run on mobile devices. Recall that the first iPhones had severely limited RAM (128MB!) and CPUs, and even when, years later, Android devices with Flash bundled were released, they couldn't run it terribly well. Flash was also a massive security and stability headache: as Apple loved to point out, it was the single largest source of application crashes on OS X.
- crwll 12y agoFlash existed for Symbian OS (think Nokia smartphones) way before there was iPhones, and those devices naturally had even lower hardware specs. (I still agree that not supporting Flash was the correct choice for Apple, though.)
- TazeTSchnitzel 12y ago> Flash existed for Symbian OS (think Nokia smartphones) way before there was iPhones, and those devices naturally had even lower hardware specs. I'm well aware! I had an HP iPaQ "Pocket PC" for a long time, and you could run a stripped-down version of Flash on it. But it ran slowly, and it only really worked for simple animations. You couldn't use something like YouTube on it, and it's things like YouTube that were the killer app for Flash.
- 0x0 12y agoThe flash thing that existed for symbian was not "Flash", it was "FlashLite", a very different plugin that supported exactly 0 of all the .swf files I tried to throw at it, including even super simple animations.
- 0x0 12y agoEven though Apple was right in the end, I think calling Apple "arrogant" is quite on the mark. It is they who denied opening up MobileSafari for 3rd party plugins (yet it supports 1st party plugins; in earlier versions you could even iterate the navigator.plugins property and see quicktime there). I remember seeing Adobe hinting heavily that they even had a working flash plugin (for jailbroken phones?) going internally. In fact, I think early Adobe Air applications targeting iOS shipped with an embedded flash player engine, until Apple started rejecting all applications "not compiled with apple-gcc from objective-c" and banning "interpreted code", so Adobe even went as far as writing an AS3 LLVM compiler, so that newer Adobe Air applications were compiled down to native arm assembly with no flash runtime present. See for example http://web.archive.org/web/20130302154428/http://www.adobe.com/devnet/logged_in/abansod_iphone.html http://web.archive.org/web/20130302154428/http://www.adobe.c... I bet the real reason for blocking flash player in Mobile Safari was to block all the flash based ad banners of the day. It would have degraded battery life and the user experience quite a lot.
- leeoniya 12y ago> I understand your frustration, but I think you're complaining that you didn't get an option that was never realistically on the table in the first place. Your respect for the W3C matters a lot less to them than millions of people being able to watch content produced by a billion dollar industry, which much of that industry simply isn't willing to make available without DRM-style safeguards at the present time. I don't know why you're getting downvoted. I also gather downvotes whenevver I make a comment like this. The current crop of content producers will not produce content without some guarantees/safeguards. There was never an option to outright refuse these conditions because we would simply be left with no content at all or it would be completely locked to proprietary hardware and/or platforms.
- TazeTSchnitzel 12y agoIf their only option is to produce content without "safeguards", they'll produce it without safeguards. Content will be pirated regardless of whether browsers have DRM.
- leeoniya 12y agoIt's not a question about the reality of the piracy situation, because that hasn't changed since the VHS copy protection days. Simply having some sort of protection there - no matter how ineffective - gives them legally-effective leverage to go after those bypassing it. You cannot, as a stakeholder (content producer, actor, etc), argue in good conscience for no protection whatsoever in a commercial venture. Yes, there is a major distribution, availability, region and device-lockdown issue to be solved. But removing all protection is just the brute-force, blanket solution that is understandably one-sided and thus unworkable.
- TazeTSchnitzel 12y ago> Simply having some sort of protection there - no matter how ineffective - gives them legally-effective leverage to go after those bypassing it. Use JavaScript, then.
- 12y ago
- TillE 12y ago> For those users, a lot of major sites still "don't work properly" today because of Apple's arrogance. How well did Flash on Android work? The answer is "not very". Jobs was (apparently) entirely correct when he wrote that Adobe was never able to show him a version of mobile Flash that wasn't complete garbage.
- Touche 12y agoIt worked fine, actually. Considering that was a good 5 years ago and phones were a fraction as fast as the ones today, you could watch videos and play games (Kongregrate had a section for touch flash games that worked very well). Adobe abandoned it simply because the effort required to maintain it was too high considering they were never going to be on iOS.