Hacker News Reader

Comment by tarsinge | Hacker News Reader

It will not change until dev stop developing on Chrome as their main browser. Maybe tooling could be an excuse for very large webapps, but otherwise and especially for websites (hello simple forms broken except if you use Chrome) it's definitely not.

Also it's orthogonal with JS usage, anecdotically I mainly work on JS heavy websites and don't use Chrome.

View on HN

I dev in Firefox. It’s great! The tooling’s really good. It’s subtly different from Chrome and you’ll feel a twinge of friction moving, but by and large, it’s easy.

Just shut it down and restart it every couple of days because it’s memory usage isn’t as tight.

Are you using the Firefox Developer Edition[1], or just the current stable one?

Fellow web-dev here, using Firefox (the one that comes with Ubuntu) as main driver. And I'd like to know if the Developer Editiion offers any benefits over the stable one, for webdevelopment.

[1] https://www.mozilla.org/nl/firefox/developer/

Yes, I use the developer edition. TBH I’m not aure what the benefits are! ;-)

I do too, but what I miss is customized throttling settings (I need to optimize for fast overseas connections: high bandwidth but also high latency). Chrome (and Edge) have this.

Firefox has this too. You can do it the network tab[1] or in the Responsive Design Mode[2]. There's drop downs there where you can control how much you want to throttle

[1] https://developer.mozilla.org/en-US/docs/Tools/Network_Monit...'

[1] https://developer.mozilla.org/en-US/docs/Tools/Responsive_De...

Thanks, I know these settings. One can only choose from the predefined settings. You can't customize those (as for me, to high bandwidth and high latency).

Reply on news.ycombinator.com