News for hackers. Stuff that matters.

A comment on No to Chrome. Parent comment

Re:No to Chrome by philliphaydon on Friday December 06, 2019 @08:43AM (#21721658)
FF just got web socket inspectors so I really don't know what chrome dev tools has now. Everything about ff dev tools is better. Especially looking at css layouts.
[ Parent | on HN ]
Re:No to Chrome by RoryH on Friday December 06, 2019 @09:25AM (#21721976)
As a web dev, I find the FF dev tools a good bit less performant, but I still try to use it always without reverting to Chrome.. The one feature I have not found in FF dev tools is Search, this is very handy for find random JavaScript on a JS heavy site.

Edit: This post prompted me to Google for it: https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_...

Move along, nothing to see.. :-\

[ Parent | on HN ]
Re:No to Chrome by digitarald on Friday December 06, 2019 @10:02AM (#21722329)
Also, Network full-test search is now in the Network panel
[ Parent | on HN ]
Re:No to Chrome by RonanTheGrey on Friday December 06, 2019 @04:44PM (#21726267)
Well, I need to try the FF dev tools again, it's been about a year since I did and they were missing some critical things.

Looking good, will give it another go.

[ Parent | on HN ]
Re:No to Chrome by jessewmc on Friday December 06, 2019 @10:31AM (#21722607)
This has finally allowed me to switch. I’ve been trying to since quantum came out two years ago, but this was always a deal breaker.

Firefox is generally still a little buggier and less performance in my experience, but not so much that I want to switch back. Hopefully they can stay relevant.

[ Parent | on HN ]
Re:No to Chrome by gherkinnn on Friday December 06, 2019 @11:41AM (#21723438)
CSS is better in Firefox. They also used to ship a web audio api debugger. The new scratchpad is nice too. Does 80% of what I need.

But Chromes debugger and performance analysis still is a lot more capable.

[ Parent | on HN ]