Firefox 85 cracks down on supercookies

Re:Firefox 85 cracks down on supercookies by Macha on Tuesday January 26, 2021 @03:04PM (#25920427)

There is a real cost to changing APIs/documentation/UIs. My experience talking to black (one African, one European) coworkers is their reaction is "That's the problem you're going to fix?". When the company does a companywide initative to remove "problematic" terms from APIs/documentation, but doesn't stop funding of politicians who support voter suppression that predominantly affect black people in real practical ways, that bemusement can even turn to offense as they feel placated.

Of course, my coworkers don't represent all black people, and especially wouldn't claim to represent African Americans, but if even black people can hold this opinion, are you surprised others don't see this as worth the effort to change?

[ Parent | on HN ]

Re:Firefox 85 cracks down on supercookies by ogre_codes on Tuesday January 26, 2021 @03:59PM (#25920980)

> There is a real cost to changing APIs/documentation/UIs.

This is an OSS project. If someone cares enough about it, they should submit a (non-breaking) patch along with a patch for the documentation. There are no costs to people who don't find it a valuable change.

> My experience talking to black (one African, one European) coworkers is their reaction is "That's the problem you're going to fix?".

Obviously this isn't fixing any of the fundamental issues, but it does bother some people. My preference is to respect the people who have problems with it. An easy policy is to simply avoid creating new software which uses that terminology and to accept any patches which fix it. That way the people who feel the change is important bear the burden of the cost (which is likely small some thing like this).

[ Parent | on HN ]