This is a total non-response. They're not actually under an obligation to report a bug and use their time - Mozilla, however, is obliged to make their browser work properly, and to ensure the team that's working on it is properly staffed/resourced/competent.
Your response is downplaying someone's actual concern by acting like it's wrong that they don't spend their spare time participating in open source software development.
Furthermore, this "browser monoculture" argument is ridiculous. WebKit and Blink are both open source, and Mozilla is increasingly becoming what Opera was back with Presto: a lone engine with quirks that nobody wants to waste their time working around.
If Mozilla gave up Gecko tomorrow and forked WebKit (a la what Blink is) I don't think I'd bat an eye. This is like what junior programmers wind up learning at some point - nobody cares what the code looks like, just that it does what it's expected to.
I say this all as someone who's contributed to some Mozilla repos, has a massive personal investment in Rust (and has read a good chunk of Servo, and liked it), and has been a fan since the Mozilla Suite days.
> Your response is downplaying someone's actual concern by acting like it's wrong that they don't spend their spare time participating in open source software development.
Anything that broken would be fixed, almost instantly, had they reported it. I am not very amenable to people who discuss their very extreme personal anecdotes that they have failed to even put even the basic (some may even say courteous) amount of help and instead talk about their experience like it's typical.
> Furthermore, this "browser monoculture" argument is ridiculous. WebKit and Blink are both open source, and Mozilla is increasingly becoming what Opera was back with Presto: a lone engine with quirks that nobody wants to waste their time working around.
Open source does not ensure that a monoculture will not develop; both WebKit and Blink are financed by billion (trillion?) dollar corporations that have almost complete control over what will or will not be worked on or merged in. Every engine has its own quirks and slant on how it interprets the web standard: if WebKit was the dominant browser today we'd all be even more hesitant to roll out WebM or WebGL 2.
> If Mozilla gave up Gecko tomorrow and forked WebKit (a la what Blink is) I don't think I'd bat an eye. This is like what junior programmers wind up learning at some point - nobody cares what the code looks like, just that it does what it's expected to.
Who exactly are you likening to "junior programmers"?
> I say this all as someone who's contributed to some Mozilla repos, has a massive personal investment in Rust (and has read a good chunk of Servo, and liked it), and has been a fan since the Mozilla Suite days.
And you know my personal history on this pretty well too, but you'll notice I'm advocating for Mozilla in this case.
This is a total non-response. They're not actually under an obligation to report a bug and use their time - Mozilla, however, is obliged to make their browser work properly, and to ensure the team that's working on it is properly staffed/resourced/competent.
Your response is downplaying someone's actual concern by acting like it's wrong that they don't spend their spare time participating in open source software development.
Furthermore, this "browser monoculture" argument is ridiculous. WebKit and Blink are both open source, and Mozilla is increasingly becoming what Opera was back with Presto: a lone engine with quirks that nobody wants to waste their time working around.
If Mozilla gave up Gecko tomorrow and forked WebKit (a la what Blink is) I don't think I'd bat an eye. This is like what junior programmers wind up learning at some point - nobody cares what the code looks like, just that it does what it's expected to.
I say this all as someone who's contributed to some Mozilla repos, has a massive personal investment in Rust (and has read a good chunk of Servo, and liked it), and has been a fan since the Mozilla Suite days.