Hacker News new | ask | show | jobs
by zxcvbn4038 1152 days ago
Mozilla had the same issue - it was one engineer who stubbornly kept webp support out of the browser for years. Then he quit or got laid off and Mozilla finally got support. Mozilla also refused to support Yubikey for years, which we are still paying for now. It seems to me like Mozilla forgot really quickly what life was like when Internet Explorer was the dominant browser. Half the reason Chrome can ignore community outrage is because Mozilla decided existing options were "good enough" and stopped being competition.

That said though, that FSF guy is nuts. He can't link to their bug tracker because it uses Javascript? I think that battle is lost. But he did obviously read the tracker, does this mean he has to remove his tinfoil hat and go bathe in the living waters of Richard Stallman's bathtub?

1 comments

Maybe you misread or misunderstood (although maybe it makes no difference to you), but the specific issue is: the FSF won't link to the bug tracker (not can't) because of proprietary Javascript. The FSF has no absolute rejection of JS, they just are purist about the JS being free software.

And it wasn't a personal post by an "FSF guy", it's the stance of the whole FSF organization.

Yes, the battle is lost. Fighting an effectively lost battle isn't necessarily nuts, but criticizing it is quite understandable.