4 ms·

This is a rediculous justification. Websites should not be coded to a whitelist of browsers.

kinlan 7y ago
Biased reply - I work for Google. It depends on what you choose as your choice of technology, if you choose web components then you really can only really offer that same experience to users that have a browser that supports that API natively (without polyfills) which old Edge did not do. My understanding of this situation with yt was that our server side detection code was wrong based on an update in edge (or our UA management), and we don't do feature detection in the client because it is too slow... So we send people to the older version.
- mr_toad 7y ago
  > experience Developers care a lot more about this ‘experience’ than users do. Yes it’s fun to play with the new shiny, but users don’t care. User experience is an excuse, it’s double-talk.
  - Godel_unicode 7y ago
    You appear to have somehow missed the extremely loud chorus of "we hate it, change it back" that happen every time any web app gets a new design. See also the saga of Instagram on Android.
    - kortilla 7y ago
      You appear to have misunderstood the comment you are replying to.
      - Godel_unicode 7y ago
        The same could be said of you. We'll never know, since your comment could mean anything.
- sjwright 7y ago
  Interpreting user agent strings is what amateur programmers do. I don't generally expect high standards from Google engineers (a whole other argument I won't entertain here) but that's still pretty tragic for a top-five website. And besides, your claim is doubtful at best since Chromium Edge doesn't share any User Agent string elements with previous EdgeHTML versions. Your YT developers would have needed to be intentionally malicious to match "Edg/" as a trigger to downgrade the user experience.
LoSboccacc 7y ago
yeah but blacklisting or at least conscious degradation is necessary. hit that with a game I built, had to degrade the experience on chrome/iOS because of the non-accelerated canvas element

Biased reply - I work for Google. It depends on what you choose as your choice of technology, if you choose web components then you really can only really offer that same experience to users that have a browser that supports that API natively (without polyfills) which old Edge did not do. My understanding of this situation with yt was that our server side detection code was wrong based on an update in edge (or our UA management), and we don't do feature detection in the client because it is too slow... So we send people to the older version.

mr_toad 7y ago
> experience Developers care a lot more about this ‘experience’ than users do. Yes it’s fun to play with the new shiny, but users don’t care. User experience is an excuse, it’s double-talk.
- Godel_unicode 7y ago
  You appear to have somehow missed the extremely loud chorus of "we hate it, change it back" that happen every time any web app gets a new design. See also the saga of Instagram on Android.
  - kortilla 7y ago
    You appear to have misunderstood the comment you are replying to.
    - Godel_unicode 7y ago
      The same could be said of you. We'll never know, since your comment could mean anything.
sjwright 7y ago
Interpreting user agent strings is what amateur programmers do. I don't generally expect high standards from Google engineers (a whole other argument I won't entertain here) but that's still pretty tragic for a top-five website. And besides, your claim is doubtful at best since Chromium Edge doesn't share any User Agent string elements with previous EdgeHTML versions. Your YT developers would have needed to be intentionally malicious to match "Edg/" as a trigger to downgrade the user experience.

LoSboccacc 7y ago

yeah but blacklisting or at least conscious degradation is necessary. hit that with a game I built, had to degrade the experience on chrome/iOS because of the non-accelerated canvas element