I know what he’s talking about- there was some javascript spec or something that google proposed, and nobody else bought in, so it never actually became part of javascript’s standard.
But google implemented it into chrome’s javascript engine anyway, and then used it for youtube. There was some fallback code if the new functions weren’t available, but, because of a ‘mistake’ they didn’t work and basically made playback ass for a while until the open source community basically debugged and fixed the issue FOR google, and then spent a few weeks cramming it down google’s throat that it needed fixed.
It probably didn’t have anything to do with Firefox itself. It’s likely related to something I messed up in FF or it was something to do with the ancient laptop I had at the time being a junk heap, but I tried Chrome and noticed that the trouble didn’t exist there. So I started using Chrome.
I kept using it because of all the google integration, which was really handy when I was using the google business suite to run my own small business. I shut that down two years ago now, so there’s nothing really keeping me on Chrome any more.
I swapped back to FF a few days ago and YouTube works fine now. So I’m back on the FF train and giving Google the finger the whole way over banning the adblockers that I liked.
Yeah if you fiddle around with about:config without knowing exactly what yer doing, shit breaks. Fortunately you can type “about:profiles” in the url box, make a test profile, and mess around as much as you want before nuking your default browser.
never had a problem with firefox and youtube
The only problem I’ve had is that you can’t view HDR content in YouTube on Firefox.
That’s not a big part of YouTube (yet), so it is largely unnoticeable.
I know what he’s talking about- there was some javascript spec or something that google proposed, and nobody else bought in, so it never actually became part of javascript’s standard.
But google implemented it into chrome’s javascript engine anyway, and then used it for youtube. There was some fallback code if the new functions weren’t available, but, because of a ‘mistake’ they didn’t work and basically made playback ass for a while until the open source community basically debugged and fixed the issue FOR google, and then spent a few weeks cramming it down google’s throat that it needed fixed.
google does this kinda shit on purpose to reinforce their market position
One of the many reasons why Google should be splitted into different companies
Isn’t it? YouTube isn’t its own company?
He means separate companies with few or no ties with each other.
It probably didn’t have anything to do with Firefox itself. It’s likely related to something I messed up in FF or it was something to do with the ancient laptop I had at the time being a junk heap, but I tried Chrome and noticed that the trouble didn’t exist there. So I started using Chrome.
I kept using it because of all the google integration, which was really handy when I was using the google business suite to run my own small business. I shut that down two years ago now, so there’s nothing really keeping me on Chrome any more.
I swapped back to FF a few days ago and YouTube works fine now. So I’m back on the FF train and giving Google the finger the whole way over banning the adblockers that I liked.
It probably did. Google has been caught red-handed with messing with Youtube to break Firefox.
https://www.reddit.com/r/youtube/comments/17z8hsz/youtube_has_started_to_artificially_slow_down/
Jesus Christ, what a bunch of rat-fuckers.
Yeah if you fiddle around with about:config without knowing exactly what yer doing, shit breaks. Fortunately you can type “about:profiles” in the url box, make a test profile, and mess around as much as you want before nuking your default browser.