9 engineers on Hacker News describe using Chrome DevTools first-hand: 2 endorse it, 0 regret it, 2 are mixed.
“Firefox and Chrome these days support debugging source mapped files... They're buggy and make the browser very slow.”
mixed · production · nawitus · 2014-10-03 · source ↗ · wrong label?“It was fascinating to pause code and just hover over different bits of code variables / parameters and see the data being transformed.”
endorse · personal · hu_me · 2014-09-29 · source ↗ · wrong label?“Chrome is a little buggy setting breakpoints in large codebases, but restarting the browser usually fixes it.”
mixed · production · mmastrac · 2013-12-25 · source ↗ · wrong label?“I also automate common debugging steps with chrome snippets to save time.”
neutral · production · greenyouse · 2021-06-12 · source ↗ · wrong label?“the Chrome network monitor DOES NOT show the retry which makes it even more confusing.”
neutral · production · joshstrange · 2019-10-18 · source ↗ · wrong label?“When developing, I can use Chrome Dev Tools. On prod, I have to copy paste.”
neutral · production · leerob · 2019-02-18 · source ↗ · wrong label?“I've been using Chrome's dev tools for quite a while now.”
neutral · personal · mercer · 2016-12-21 · source ↗ · wrong label?“I've just been using the iPhone user agent "simulation" in Chrome's dev tools.”
neutral · personal · mladenkovacevic · 2013-12-03 · source ↗ · wrong label?