4 ms·
> 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 cl
by 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.
- TazeTSchnitzel 12y ago> It is they who denied opening up MobileSafari for 3rd party plugins ...how is that arrogant? They wanted to only allow standard technologies? What is wrong with that? > yet it supports 1st party plugins; in earlier versions you could even iterate the navigator.plugins property and see quicktime there It had "quicktime" as a "plugin" but I believe that just launched the video player. Similarly, Apple replaced YouTube video embeds (Flash) with the video player. No plugins there. > I remember seeing Adobe hinting heavily that they even had a working flash plugin (for jailbroken phones?) going internally. Yes, Adobe did. It didn't work very well. > 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. Flash period would ruin battery life. Similar to why iOS has no multitasking.
- Silhouette 12y agoFlash was also proprietary. It's closed-source, patent-encumbered, and has a single implementation. It's completely under the control of Adobe. Perhaps, but I'm not sure how any of this is different to the various media extension proposals/standards we're starting to see more recently. And at least before, if you wanted to serve video from your web site, all you had to do was get one of the numerous Flash video players and prepare one version of your videos that would work in that player on almost any device. As Apple explained countless times, it is not because of "arrogance" that they did not support Flash. Please forgive me if I don't take their word for it. The thing is, Flash has run -- and reasonably well -- on numerous other mobile devices, even some from quite a few years ago, so I don't really buy the performance arguments. Even if they had been true for early generations of smartphones and tablets, the performance of these types of device was always expected to increase significantly over time, as indeed it has. If the performance would still be a problem on today's iOS devices then presumably Apple's users would opt for other implementations instead, but as far as I'm aware, Apple still have an effective monopoly on distribution of software that runs on iOS devices, and they can and do block anything they don't like for sometimes not entirely clear (or, some might argue, entirely fair) reasons. So no-one was ever allowed to decide whether Flash running on a modern iPhone or iPad would have been OK, because that option was removed from the table, and we were left with devices that have bugs and/or non-standard behaviours in basic functionality. 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. Leaving aside the disturbing implications of Apple actually having a reliable data set on which to base such a claim, browsers are a constant security and stability headache. Take a look at the release notes for Chrome or Firefox, and see how often that little update every few weeks includes at least one critical security update, and how often they have glitches so bad they have to push an out-of-band update instead of waiting just a few weeks. As I said before, there seems little reason to expect better results just because someone shifts things like video rendering and DRM technologies to a slightly different bit of low-level, native, closed source, patent-encumbered, even-the-browser-devs-don't-see-it code written in an error-prone language by the same kinds of development team that wrote the plug-ins.
- TazeTSchnitzel 12y ago> Perhaps, but I'm not sure how any of this is different to the various media extension proposals/standards we're starting to see more recently. Encrypted Media Extensions is an open standard. The small DRM plugins that use it aren't open, but the core standard is. You've moved from a closed, proprietary system for the entire application, to a closed system for just the DRM and nothing else. That's huge progress. > Please forgive me if I don't take their word for it. The thing is, Flash has run -- and reasonably well -- on numerous other mobile devices, even some from quite a few years ago No it hasn't. "Flash Lite" worked, but slowly, and it couldn't do anything useful. The killer app for Flash was largely video and games, both of which don't work well in Flash on phones. > Even if they had been true for early generations of smartphones and tablets, the performance of these types of device was always expected to increase significantly over time, as indeed it has. By the time Flash could run well on the iPhone, the web had largely gotten rid of Flash and it was fast becoming a legacy technology, so there was no point in supporting it. > If the performance would still be a problem on today's iOS devices then presumably Apple's users would opt for other implementations instead The performance is now irrelevant because the web has moved on from Flash. > browsers are a constant security and stability headache. Yes, they are! But adding an extra attack surface for those two fronts is never a good idea if you can avoid it. If you can avoid adding a binary blob to your browser that has frequent security issues, why wouldn't you do so? > As I said before, there seems little reason to expect better results just because someone shifts things like video rendering and DRM technologies to a slightly different bit of low-level, native, closed source, patent-encumbered, even-the-browser-devs-don't-see-it code written in an error-prone language by the same kinds of development team that wrote the plug-ins. No video rendering is done by EME, and EME doesn't and probably never will run on the iPhone.