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...
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.
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.