←back to thread

1035 points deryilz | 1 comments | | HN request time: 0.209s | source
Show context
al_borland ◴[] No.44545060[source]
Even if bigs exists to work around what Google is doing, that isn’t the right way forward. If people don’t agree with Google move, the only correct course of action is to ditch Chrome (and all Chromium browsers). Hit them where it hurts and take away their monopoly over the future direction of the web.
replies(26): >>44545103 #>>44545185 #>>44545382 #>>44545931 #>>44545951 #>>44546164 #>>44546522 #>>44546599 #>>44546664 #>>44546763 #>>44547531 #>>44548200 #>>44548246 #>>44548399 #>>44548418 #>>44548820 #>>44549698 #>>44550098 #>>44550599 #>>44551061 #>>44551130 #>>44551663 #>>44553615 #>>44554220 #>>44556476 #>>44571602 #
high_priest ◴[] No.44545103[source]
Its not happening
replies(4): >>44545238 #>>44545244 #>>44545297 #>>44545919 #
Etheryte ◴[] No.44545238[source]
I don't know, I switched to Safari and it was painful for like two hours and then I stopped thinking about it. The only thing I somewhat miss is the built-in page translate, but I don't need it often enough to be bothered much.
replies(3): >>44545267 #>>44545318 #>>44545577 #
mattkevan ◴[] No.44545318[source]
Safari has had built-in page translate for years now. It’ll detect different languages and show a translate option in the site tools menu. Works well.
replies(1): >>44545428 #
1. Etheryte ◴[] No.44545428[source]
I'm aware of this, but in my experience it's pretty bad. It doesn't even cover all European languages, never mind the rest of the world. For the languages it does support, it's always a lottery whether it works with that specific site or not. I've tried using it a few times, but it's not even remotely close to what Chrome does.