3 ms·

>that extension for Google Translate was really clunky https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/ https://addons.mozilla.org/en-US/fi

>that extension for Google Translate was really clunky https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/ https://addons.mozilla.org/en-US/firefox/addon/traduzir-pagi... This works exactly like the respective Chrome feature. >this is coming so late Because it isn't the same thing. This is done locally. (Not the linked extension but the Firefox built-in.)

tmpX7dMeXU 3y ago
A difference that doesn’t matter to most people most of the time. GP wants a translation service built in to the browser. Even if they appreciate it being local-only, coming back with “no, here’s some largely irrelevant technical difference that makes this better!” misses the point.
- samtheprogram 3y ago
  It's Mozilla, so most of their users do care. And if they don't, the extension with the same capabilities as Chrome already existed.
- deleted 3y ago
  [deleted]
- capableweb 3y ago
  > A difference that doesn’t matter to most people most of the time. This seems to be about the first time I see Mozilla knowing its own users better than a random HN user know Mozilla's users. Mozilla/Firefox is meant for users who care about privacy, it's literally the first taglines you see when visiting the landing pages for Mozilla or Firefox. So, with this newfound knowledge about who is using Firefox and who is using other browsers like Google Chrome, maybe now it makes sense why Firefox wanted local translations instead of sending them off somewhere else?