5 ms·

Why do so many find it necessary to downvote my comment? MediaSourceExtensions are vital for supporting media in Safari (and already available in iPadOS and Ma

Why do so many find it necessary to downvote my comment? MediaSourceExtensions are vital for supporting media in Safari (and already available in iPadOS and MacOS [and under the hood on iOS for VP8/9 support]) and the fullscreen API for arbitrary elements is necessary to support video + slides (or other sideloaded material) and to support captions/subtitles that need features not supported with regular textracks.

MBCook 4y ago
I didn’t, but I’ll hazard a guess. “Safari is the new IE” has been the meme for years, despite the fact the situation is totally different. Any time Safari is mentioned or gets a new feature it’s just posts from people complaining Safari doesn’t support WebUSB or whatever their pet feature is. So Safari added the one I see people complaining about more than anything else. The top complaint on HN for literally years. And you just switched your complaining to something else. Most people here are celebrating they got something they’ve wanted forever. Personally I’m just tired of all the bitching. There is no escaping it, it seems. You could have framed your comments much more positively. Perhaps that would have helped. My 2¢ guess.
- lern_too_spel 4y ago
  It doesn't help that apologists have said Apple isn't dragging their feet but just not implementing features that are bad for users. This article is about one such feature. GP points out that Apple is still dragging their feet on features important to them, features that are only not implemented because they threaten Apple's monetization of streaming services, and apologists drag them instead of Apple. The situation with Safari and IE is very different. What is not different is that they were the most damaging browsers for progress of the web platform in their respective eras.
  - WorldMaker 4y ago
    What made IE damaging was that it raced out ahead of standards and created APIs that no one else supported but companies started to rely on while it was in the lead and couldn't migrate away to standards that didn't exist. Most people today remember the era of IE stagnation and misunderstand: that wasn't the period of danger, that the was consequences of danger. Safari isn't the new IE, Safari is the new Netscape. Chrome is the new IE in that danger period. All the web developers complaining about Safari and Firefox "being slow", that's the danger signs. That's the warning flags. That's the new IE damaging browser progress by locking people into single-browser "web standards" that aren't standards. I don't know if the web will reap the same consequences this time, if there will be a Chrome stagnation to follow this Chrome danger time. I do know that the warning signs aren't what a lot of people think they are. The warning signs are the complaints about "Safari holding back the web" because they tend to imply that Chrome is the web when it isn't.
    - lern_too_spel 4y ago
      That didn't make IE damaging. XMLHttpRequest pulled the web forward. What made IE damaging was that after it came pre-installed on Windows, it stopped progressing after IE6. It had a garbage collector that made very rich webapps nearly impossible. https://vinaytech.wordpress.com/2008/11/07/garbage-collection-in-ie6/ https://vinaytech.wordpress.com/2008/11/07/garbage-collectio... It had CSS bugs that weren't fixed for years. https://css-tricks.com/ie-css-bugs-thatll-get-you-every-time/ https://css-tricks.com/ie-css-bugs-thatll-get-you-every-time... It didn't implement features that web developers asked for and didn't even join the working group formed to standardize those features. https://en.wikipedia.org/wiki/WHATWG https://en.wikipedia.org/wiki/WHATWG It had security issues that made it dangerous for people to use the web. Safari suffers from the last three of those problems, and Apple makes them even worse by preventing other renderers on its platforms. If I had an iOS device, I'd want to run Firefox. I can't. That's on Apple, and pretending otherwise is absurd.
      - danaris 4y ago
        Right, so you remember and bring up one of the very very few features IE introduced during that period that actually turned out to be helpful and beneficial, and you gloss over the many that were emphatically not. I notice you don't mention ActiveX as being something that "pulled the web forward".
        lern_too_spel 4y ago
        ActiveX has had no impact whatsoever. How has it harmed the web platform? XHR, just like MSE, which the person who started this thread is asking for, expands the usability of the web in a vendor-neutral way. MSE, better than XHR, went through a standards process to ensure web publishers wanted it and browser vendors agreed on the API. There is no reason for Apple to drag its feet on implementing MSE on iPhones, aside from protecting Apple's profits. It is ridiculous to see people defending Apple about this.
      - WorldMaker 4y ago
        It wouldn't have mattered if IE stopped progressing after IE6 given migration to other browsers, if there weren't so many "legacy" websites and apps stuck needing IE. Even in the worst days of IE stagnation Firefox and Chrome were only an install away. (And Chrome was busy using bad adware tactics to get as many installs as possible back in those days, but that's a different complaint in a different conversation.) What made IE truly damaging/dangerous was that before it stopped progressing it had lots of great "pull the web forward" features like XHR and CSS box-sizing that yesterday's developers wrote "bleeding edge" apps on that became those very same "legacy" sites and apps when the stagnation hit. While the web eventually standardized things like XHR and CSS box-sizing, they were done in ways that made migration of those "single browser apps" just slightly uncomfortable enough so companies especially procrastinated staying on the stagnant browser as long as possible to avoid paying down tech debt in their "legacy" apps. Today's "bleeding edge" apps are tomorrow's "legacy apps", and people aren't building "bleeding edge" apps for Safari [0], but they are building Chrome-only "bleeding edge" apps using all the little things that are like XHR in their own ways (WebUSB, Speech Recognition, what have you). The danger is that there are far too many of them. Again, I can't predict the future and I can't assume that Google execs are dumb enough to do the exact same thing that Microsoft did: check their (current!) marketshare, declare themselves the winner, and decide to finish Chrome as a project, moving the development team to more important tasks to the corporate bottom line. I want to believe that the pursuant stagnation would be less overall a dark period for the web because plenty of Chromium forks exist, but the install base is huge and convincing them all to switch to a fork would still be a massive marketing effort that wouldn't happen overnight. But stagnation is the consequence of the danger of people building single-browser apps, it's not the danger itself. The canaries (Safari, Firefox) are dying and blaming the canaries for being weak is avoiding asking hard questions about if the web is currently safe or not. > Apple makes them even worse by preventing other renderers on its platforms. If I had an iOS device, I'd want to run Firefox. I can't. That's on Apple, and pretending otherwise is absurd. That is a different, unrelated problem than comparisons to IE. Even when pre-installed on Windows IE never stopped people from installing other browsers or setting them the default. It got real unfriendly about it in some versions of Windows, but it never (could have) blocked them entirely. That's still a problem to deal with, and maybe even a major problem, though these days iOS and Android are pretty neck-and-neck in the market and iOS does not have the domination it once had even in the US. But it's not at all the same problem as IE was. [0] Anymore; I will admit there was a brief period early in the rise of iOS with -webkit- prefixed everything where it was a small concern.
- phillipseamore 4y ago
  Thanks for the notes MBCook. I certainly know the noise in the comments here when Safari is discussed. And that's why I only gripe on these two features which are available in every Safari for several years now, except on iOS, with no apparent reason.

MBCook 4y ago

I didn’t, but I’ll hazard a guess. “Safari is the new IE” has been the meme for years, despite the fact the situation is totally different. Any time Safari is mentioned or gets a new feature it’s just posts from people complaining Safari doesn’t support WebUSB or whatever their pet feature is. So Safari added the one I see people complaining about more than anything else. The top complaint on HN for literally years. And you just switched your complaining to something else. Most people here are celebrating they got something they’ve wanted forever. Personally I’m just tired of all the bitching. There is no escaping it, it seems. You could have framed your comments much more positively. Perhaps that would have helped. My 2¢ guess.

lern_too_spel 4y ago
It doesn't help that apologists have said Apple isn't dragging their feet but just not implementing features that are bad for users. This article is about one such feature. GP points out that Apple is still dragging their feet on features important to them, features that are only not implemented because they threaten Apple's monetization of streaming services, and apologists drag them instead of Apple. The situation with Safari and IE is very different. What is not different is that they were the most damaging browsers for progress of the web platform in their respective eras.
- WorldMaker 4y ago
  What made IE damaging was that it raced out ahead of standards and created APIs that no one else supported but companies started to rely on while it was in the lead and couldn't migrate away to standards that didn't exist. Most people today remember the era of IE stagnation and misunderstand: that wasn't the period of danger, that the was consequences of danger. Safari isn't the new IE, Safari is the new Netscape. Chrome is the new IE in that danger period. All the web developers complaining about Safari and Firefox "being slow", that's the danger signs. That's the warning flags. That's the new IE damaging browser progress by locking people into single-browser "web standards" that aren't standards. I don't know if the web will reap the same consequences this time, if there will be a Chrome stagnation to follow this Chrome danger time. I do know that the warning signs aren't what a lot of people think they are. The warning signs are the complaints about "Safari holding back the web" because they tend to imply that Chrome is the web when it isn't.
  - lern_too_spel 4y ago
    That didn't make IE damaging. XMLHttpRequest pulled the web forward. What made IE damaging was that after it came pre-installed on Windows, it stopped progressing after IE6. It had a garbage collector that made very rich webapps nearly impossible. https://vinaytech.wordpress.com/2008/11/07/garbage-collection-in-ie6/ https://vinaytech.wordpress.com/2008/11/07/garbage-collectio... It had CSS bugs that weren't fixed for years. https://css-tricks.com/ie-css-bugs-thatll-get-you-every-time/ https://css-tricks.com/ie-css-bugs-thatll-get-you-every-time... It didn't implement features that web developers asked for and didn't even join the working group formed to standardize those features. https://en.wikipedia.org/wiki/WHATWG https://en.wikipedia.org/wiki/WHATWG It had security issues that made it dangerous for people to use the web. Safari suffers from the last three of those problems, and Apple makes them even worse by preventing other renderers on its platforms. If I had an iOS device, I'd want to run Firefox. I can't. That's on Apple, and pretending otherwise is absurd.
    - danaris 4y ago
      Right, so you remember and bring up one of the very very few features IE introduced during that period that actually turned out to be helpful and beneficial, and you gloss over the many that were emphatically not. I notice you don't mention ActiveX as being something that "pulled the web forward".
      - lern_too_spel 4y ago
        ActiveX has had no impact whatsoever. How has it harmed the web platform? XHR, just like MSE, which the person who started this thread is asking for, expands the usability of the web in a vendor-neutral way. MSE, better than XHR, went through a standards process to ensure web publishers wanted it and browser vendors agreed on the API. There is no reason for Apple to drag its feet on implementing MSE on iPhones, aside from protecting Apple's profits. It is ridiculous to see people defending Apple about this.
    - WorldMaker 4y ago
      It wouldn't have mattered if IE stopped progressing after IE6 given migration to other browsers, if there weren't so many "legacy" websites and apps stuck needing IE. Even in the worst days of IE stagnation Firefox and Chrome were only an install away. (And Chrome was busy using bad adware tactics to get as many installs as possible back in those days, but that's a different complaint in a different conversation.) What made IE truly damaging/dangerous was that before it stopped progressing it had lots of great "pull the web forward" features like XHR and CSS box-sizing that yesterday's developers wrote "bleeding edge" apps on that became those very same "legacy" sites and apps when the stagnation hit. While the web eventually standardized things like XHR and CSS box-sizing, they were done in ways that made migration of those "single browser apps" just slightly uncomfortable enough so companies especially procrastinated staying on the stagnant browser as long as possible to avoid paying down tech debt in their "legacy" apps. Today's "bleeding edge" apps are tomorrow's "legacy apps", and people aren't building "bleeding edge" apps for Safari [0], but they are building Chrome-only "bleeding edge" apps using all the little things that are like XHR in their own ways (WebUSB, Speech Recognition, what have you). The danger is that there are far too many of them. Again, I can't predict the future and I can't assume that Google execs are dumb enough to do the exact same thing that Microsoft did: check their (current!) marketshare, declare themselves the winner, and decide to finish Chrome as a project, moving the development team to more important tasks to the corporate bottom line. I want to believe that the pursuant stagnation would be less overall a dark period for the web because plenty of Chromium forks exist, but the install base is huge and convincing them all to switch to a fork would still be a massive marketing effort that wouldn't happen overnight. But stagnation is the consequence of the danger of people building single-browser apps, it's not the danger itself. The canaries (Safari, Firefox) are dying and blaming the canaries for being weak is avoiding asking hard questions about if the web is currently safe or not. > Apple makes them even worse by preventing other renderers on its platforms. If I had an iOS device, I'd want to run Firefox. I can't. That's on Apple, and pretending otherwise is absurd. That is a different, unrelated problem than comparisons to IE. Even when pre-installed on Windows IE never stopped people from installing other browsers or setting them the default. It got real unfriendly about it in some versions of Windows, but it never (could have) blocked them entirely. That's still a problem to deal with, and maybe even a major problem, though these days iOS and Android are pretty neck-and-neck in the market and iOS does not have the domination it once had even in the US. But it's not at all the same problem as IE was. [0] Anymore; I will admit there was a brief period early in the rise of iOS with -webkit- prefixed everything where it was a small concern.
phillipseamore 4y ago
Thanks for the notes MBCook. I certainly know the noise in the comments here when Safari is discussed. And that's why I only gripe on these two features which are available in every Safari for several years now, except on iOS, with no apparent reason.