This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Moving to firefox would still be rolling over and taking it though. If they don’t comply, you just don’t have permission to view the web page. It’s not like they’re going to go around that in any way.
Unless you find an alternative to the website itself you’re out of options.
The only ways of “not taking it” that I would see are either you find a way to ignore the DRM and view the site anyway, or you make the site drop the implementation, neither of which switching to Firefox does.
It makes it more expensive to implement the DRM. Companies always consider things in terms of return on investment. If implmenting it gains x, but loses y% share of users, they will weigh it up, the more %ge of users on Firefox, the more it will cost and the less likely companies are to roll this out.
I mean…have you seen the gaming market on DRM? People point to arguments and research that it doesn’t even work and it still gets implemented in the AAA games…Firefox is going to need a lot more than outrage to build a share that threatens that.
DRM in games exists because their market accepts that. There is no real opposition. They already shed the people that cared about that. They can make more money from the DRM and extra stuff. This isn’t clear in browsers.
As for AAA, it’s dead to many, and indie game dev is getting stronger and stronger.
“Google controls 3/4 of the web, so not only am I going to roll over and take it, but I’m going to lube myself up for their convenience.”
FTFY
Moving to firefox would still be rolling over and taking it though. If they don’t comply, you just don’t have permission to view the web page. It’s not like they’re going to go around that in any way.
Unless you find an alternative to the website itself you’re out of options.
The only ways of “not taking it” that I would see are either you find a way to ignore the DRM and view the site anyway, or you make the site drop the implementation, neither of which switching to Firefox does.
Or just don’t visit websites that have DRM. Any website willing to work with Google on this DRM thing is a website I have zero desire to ever visit.
That kindof argument is just naïve bordering obnoxious. It’s like an ostrich putting their head into the ground.
It’s going to spread, more sites will use that DRM, and even if you decide you can keep off of them on principle, most people won’t.
If it were remotely going to end up that way we wouldn’t have chrome being able to do this to begin with
It makes it more expensive to implement the DRM. Companies always consider things in terms of return on investment. If implmenting it gains x, but loses y% share of users, they will weigh it up, the more %ge of users on Firefox, the more it will cost and the less likely companies are to roll this out.
I mean…have you seen the gaming market on DRM? People point to arguments and research that it doesn’t even work and it still gets implemented in the AAA games…Firefox is going to need a lot more than outrage to build a share that threatens that.
DRM in games exists because their market accepts that. There is no real opposition. They already shed the people that cared about that. They can make more money from the DRM and extra stuff. This isn’t clear in browsers.
As for AAA, it’s dead to many, and indie game dev is getting stronger and stronger.
I really doubt that, but I guess we’ll see.
Oh fuck you.
Oh great, now you’re getting emotional.
You aren’t providing reasonable criticism to the argument. It’s completely unrealistic and ignoring how we got here to begin with.
He’s right to respond emotional when you just make a completely unrealistic argument.