Re:Localisation is too hard for Gmail
by julianlam on Wednesday October 21, 2020 @09:18AM
(#24847541)
You can call them low priority bugs all you want, but Gmail has been around for over a decade and I'm betting their team employs at least 50 developers... Surely one of them could fix it?
Re:Localisation is too hard for Gmail
by karottenreibe on Wednesday October 21, 2020 @10:33AM
(#24848247)
It's likely not getting fixed because the opportunity costs are higher than the reward of fixing it:
https://erikbern.com/2020/03/10/never-attribute-to-stupidity...
Re:Localisation is too hard for Gmail
by reaperducer on Wednesday October 21, 2020 @11:53AM
(#24849022)
"Opportunity costs" are very often, as in this case, just an excuse for being too lazy to do the right thing.
When people have pride in their work and want to put out a quality product, instead of "optimizing" for pennies, then things get fixed.
Probably an oversight or a low priority bug for the Gmail team.
Could also be something complicated in the underlying infrastructure that makes it difficult but I see no reason why it couldn't be abstracted and managed in the frontend as part of localization. Its always easier to talk about things and handwave without understanding problems that may cause with other underlying architecture.