> In mid-2024, he pointed out its "Original Sin" of adopting digital rights management.
I disagree on that one. Maybe it could have been an option 15-20 years ago, when Firefox was a significant force. But now, if it didn't have DRM, platforms that use DRM would just tell people to use another browser, or a specialized app. And people who are not activists would just switch to "the browser that runs $service", and then you give free reign to whoever controls these browsers, including making the DRM more restrictive and more invading.
DRM is an addon, it lets you do thing that you can't do without (i.e. watching protected content), but it won't affect non-DRM content. You can turn it off if you want, you just won't be able to watch Netflix (or whatever), making it a worse user experience.
If you refuse to support DRM (and therefore denying your users of some content), hoping that it will discourage adoption of DRM by platforms, you have to keep your users captive so that they won't just switch. And considering that Firefox doesn't rely on lock-in: they don't have the means to do so, and it is against the spirit in the first place, they have to offset that by offering something else. And unfortunately, they don't have much to offer besides ideology.
The original sin, if we can call it that, is that Firefox technically lagged behind Chrome: slower, more bugs, less secure,... Having to accept DRM, as well as anything Google decided was standard is a consequence of that.
That's why I had high hopes with Servo. It had the potential to make Firefox a "better browser", giving them some weight when deciding not to support some anti-feature, but they lost it.
They also lost an opportunity on mobile by not supporting extensions for too long, and generally, for not being taken seriously. Why did it take them so long to support DNS-over-HTTPS for instance?
Now, they have an opportunity regarding ad-blocking, I don't know how they are going to waste that one, but knowing them, they are probably going to manage it.