370written posts
offlinecurrently
ok everyone's been mentioning it and i'm clueless & i hope you don't mind me asking, but what's the diff between chromes dev tools and say... dev tools of other browsers? i always glance over them and they seem similar to me but i also feel like i've only shallowed scratched their surface of them? ah! i'm so glad you asked! there are a few things about chrome's dev tools that firefox hasn't caught up on. one aspect of chrome is its ability to track event listeners on each element, and the ancestors of that element; very handy for javascript debugging. another is chrome's performance tab; it tracks GPU and CPU usage, which is huge to help you identify why your web app is causing fans to spin up (such as if your page is caught in an infinite loop, as was the case at my last job). finally, chrome's local overrides are amazing. you can load in your own CSS or JS file and refresh the page to see that file in action -- firefox doesn't do this (yet), you have to redeploy to your server. i use that one often. you might notice that most of these things are more helpful for javascript development. so if you're not into that so much, firefox's dev tools are, imo, better for HTML/CSS development. it's come a long way from the old firebug days.
|
After over 17 years, I've decided to move on from ProBoards. If you need to contact me, find me on my website.
|