4 ms·
Adobe capitulated, but apple killed it when it didnt support it on ios.
by netcraft 3y ago
Adobe capitulated, but apple killed it when it didnt support it on ios.
- neverdied 3y agoapple killed it after Jobs had a hissy fit
- liquidpele 3y agoAndroid did support it for a time though, it was a pretty good selling point in fact... but then google dropped it too :(
- kergonath 3y agoGoogle never dropped it. Adobe did, when they realised that they could make money from HTML5 instead: https://web.archive.org/web/20170114145431/https://blogs.adobe.com/conversations/2011/11/flash-focus.html https://web.archive.org/web/20170114145431/https://blogs.ado... .
- keepamovin 3y agoI'm working on bringing Flash to iOS via browser proxy^0. Basically, what we do is run the browser on the server and stream the viewport to your regular mobile browser (ie, Safari). Then we use Ruffle injected into the remote page. Basically it's a "monkey patch" to give you extensions-like capabilities but on mobile devices! 0: https://github.com/BrowserBox/BrowserBox/issues/424 https://github.com/BrowserBox/BrowserBox/issues/424
- circuit10 3y agoI remember using a browser called Puffin that worked like this to use Flash on iOS
- sundarurfriend 3y agoI'm no Apple fan, but Apple killed it because Adobe was letting Flash be an awful, unreliable piece of software for years, and seemed fine with letting that be the status quo for a decade more. If Adobe did a better job of improving the stability and resource management of the Flash clients, they wouldn't have had to "capitulate".
- phendrenad2 3y agoCitation needed. Flash wasn't particularly more unreliable or awful than browsers were. I think that flash got a bad rap because browser vendors didn't like it's monopoly on content and they wanted a slice.
- justinclift 3y ago> Flash wasn't particularly more unreliable or awful than browsers were. Citation needed. Saying that because Flash was widely touted as a significant contributor to browser crashes. Though, looking for a citation for that myself just now... all of the search results I'm getting back are just an endless sea of "Flash crashed my browser" type of things instead. :/
- phendrenad2 3y agoYeah, exactly. Just because everyone says it doesn't make it so, and the general public are often wildly wrong about basic computer facts.
- justinclift 3y agoWell, neither of us seem to have supporting evidence so far... ;) --- Using some different search parameters is turning up some results: * http://web.archive.org/web/20140903235611/https://crash-analysis.mozilla.com/bsmedberg/flash-summary.html http://web.archive.org/web/20140903235611/https://crash-anal... * https://wiki.mozilla.org/CrashKill/Flash https://wiki.mozilla.org/CrashKill/Flash * https://wiki.mozilla.org/CrashKill/Flash_Breakdown_Data https://wiki.mozilla.org/CrashKill/Flash_Breakdown_Data There is some talking around the problem on the old Mozilla Blog: * https://blog.mozilla.org/en/mozilla/firefox-3-6-4-with-crash-protection-now-available/ https://blog.mozilla.org/en/mozilla/firefox-3-6-4-with-crash... Things being about a decade old is adding further difficulty. :/
- deleted 3y ago[deleted]
- kergonath 3y agoAdobe worked on it, and even they could not show anything convincing. This was the time when Flash was causing the vast majority of crashes on OS X. Even on Android they could not make it work reliably and it was plagued with security, performance, and overheating issues. Adobe had stopped trying years before Apple officially stopped caring.