Did Google Cripple Edge’s YouTube Performance?
1–10 of 55 posts
Re: Did Google Cripple Edge’s YouTube Performance?
#2I still run Youtube Classic.
Re: Did Google Cripple Edge’s YouTube Performance?
#3Oh and also, EdgeHTML might not have been the best engine but saying it "sucks shit" is a bit extreme.
Re: Did Google Cripple Edge’s YouTube Performance?
#4Well Youtube performance used to suck under Firefox as well to the point that I felt that running youtube without the addon "Youtube Classic" in firefox was unbearable. I still run Youtube Classic.
Re: Did Google Cripple Edge’s YouTube Performance?
#5Well Youtube performance used to suck under Firefox as well to the point that I felt that running youtube without the addon "Youtube Classic" in firefox was unbearable. I still run Youtube Classic.
Playback or rendering ? I know my browser has performance issues because it doesn't have hardware-accelerated playback for VP9, I don't know if FF is in the same basket (sounds like it might be). Having an addon that only enables h264 solves that.
Re: Did Google Cripple Edge’s YouTube Performance?
#6Earlier quoted context omitted.
Playback or rendering ? I know my browser has performance issues because it doesn't have hardware-accelerated playback for VP9, I don't know if FF is in the same basket (sounds like it might be). Having an addon that only enables h264 solves that.
Afaik YouTube uses user agent sniffing to use slower functions for Firefox.
Re: Did Google Cripple Edge’s YouTube Performance?
#7Re: Did Google Cripple Edge’s YouTube Performance?
#8Earlier quoted context omitted.
Afaik YouTube uses user agent sniffing to use slower functions for Firefox.
YouTube started using Shadow DOM V0 (which is deprecated) some time ago, which is implemented only in Chrome/Chromium, as a result all other browsers render it slower.
https://arstechnica.com/gadgets/2013/01/google-maps-windows-...
Re: Did Google Cripple Edge’s YouTube Performance?
#9Re: Did Google Cripple Edge’s YouTube Performance?
#10It's much more likely that Google was trying to improve their user experience by working around an IE bug, than deliberately harming their user experience for a PR article.