|
|
|
|
|
by latexr
231 days ago
|
|
So first they didn’t do it because of the maintenance burden, and now it’s because the feature sucks and shouldn’t exist. If you’re going to keep ignoring my points and making up new things while moving the goalposts, I don’t see the point in having a discussion. I’ll say it again: > Plugging your ears and coming up with excuses doesn’t move the needle. Accept it or don’t, it makes no difference. |
|
> If you’re going to keep ignoring my points and making up new things while moving the goalposts, I don’t see the point in having a discussion.
I'm not ignoring anything - it's called disagreeing with your points. Because I do disagree with them, to an extent.
I agree that Firefox is missing features. I DO NOT agree that this is generally, keyword generally, a bad thing.
Also, Firefox is not even the most behind browser. Uh, that would be Safari, and it's not even close.
If you don't support Firefox but you DO support Safari, then:
1. You must not give a flying fuck about web standards or features, as Safari is missing the most of both OR
2. You squarely target primarily Apple users so you have no choice but to put up with Apple's subpar software, i.e. you're Stockholm'd in
For option 2, the only way to stop that is to do what I said - stop playing Apple's games and don't target their bespoke barely-functional bullshit.
Also, let me just say: there is absolutely no shame in number 2. You have to make your money. Just a couple years ago, I was maintaining an application that still targeted IE 6. Yes, really. Sometimes you have to do what you have to do to reach the users where they are.