Re:Google to restrict modern ad blocking Chrome extensions t...
by droobles on Wednesday May 29, 2019 @04:30PM
(#20045056)
Modern firefox is an awesome experience. The only reason I use Chrome is because the dev tools are that good.
[ Parent
| on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t...
by redwards510 on Wednesday May 29, 2019 @04:43PM
(#20045231)
Don't forget there is a Firefox Developer version that includes additional devtools.
Re:Google to restrict modern ad blocking Chrome extensions t...
by JMTQp8lwXL on Wednesday May 29, 2019 @09:22PM
(#20047485)
Devtools are baked into standard chrome. I find it odd I'd have to download a special version of Firefox made for developers.
Re:Google to restrict modern ad blocking Chrome extensions t...
by pitterpatter on Thursday May 30, 2019 @04:51AM
(#20049465)
Devtools are also in standard firefox. The developer edition just includes new features that haven't yet made it to the current release. The chrome analog is Chrome Dev (https://www.google.com/chrome/dev/)
Firefox: Nightly -> Developer -> Beta -> Stable -> Extended Support Release
Chrome: Canary -> Dev -> Beta -> Stable
Re:Google to restrict modern ad blocking Chrome extensions t...
by anticensor on Saturday June 01, 2019 @08:10AM
(#20068788)
Firefox is actually Nightly->Beta->Stable->ESR, where Developer Edition is a differently configured build of Beta.
Re:Google to restrict modern ad blocking Chrome extensions t...
by hardwaresofton on Wednesday May 29, 2019 @04:40PM
(#20045179)
Do you have some reasons you prefer chrome dev tools to FF? I consider FF to have the more featureful devtools, for example the sheer amount of stuff under the styles tab, you can tweak fonts in browser.
I do remember back when I used chrome there would be new `console.x` features that were chrome only from time to time, but after I switched to FF I never really looked back
Re:Google to restrict modern ad blocking Chrome extensions t...
by ryanoshea on Wednesday May 29, 2019 @05:07PM
(#20045508)
Chrome's DevTools handles developing large unbundled webapps better. When your loader is reaching to the fs for thousands of source files for a single page load, Chrome performs significantly better than Firefox. Same goes for Ctrl+P jumping to files and debugging performance.
It's gotten a lot better over the last two years, especially when FF DevTools got support for source maps and TypeScript debugging, but it still lags enough to keep me using Chrome for my job, Firefox at home.