Hacker News new | past | comments | ask | show | jobs | submit login

> Have been using Firefox for a long time, no issues, though long ago when I had little memory, Chrome was using less of it.

I'd say the only area where I still see Chrome leading a bit is for web development: when I run super-heavy JavaScript in dev mode, Chrome is faster than Firefox at executing all the JavaScript nonsense. Seen that there's no ecosystem with more turds, bloatedness and slowness than that horror that JavaScript-the-piece-of-crap is, having a browser a bit quicker at running JavaScript helps.

Long story short: for Web development, I use Chromium (it ships with Debian). For the rest I use Firefox.

> Firefox also has HTTPS-only mode...

In doubt port 80 is blocked by the firewall too.

> encrypted DNS without fallbacks,

And Firefox has a relatively easy "corporate" setting too where you can force also DNS "in the clear" over port 53 UDP (well, it's 99.9999% of the time going to be UDP so you can even firewall port 53 TCP and things shall keep working: believe me I know: theory vs practice and all that)

It's convenient if you run your own DNS resolver (which, itself, can then be forced to only use encrypted DNS).

> supports SOCKS

I confirm: a SOCKS5 proxy over ssh is always sweet.

Firefox just works.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: