4 ms·
Chrome Dev tools, the first reason why I started using Chrome. I wonder if HN has any better alternatives to suggest? I'm curious to see what I could be missing
by orliesaurus 9y ago
Chrome Dev tools, the first reason why I started using Chrome. I wonder if HN has any better alternatives to suggest? I'm curious to see what I could be missing on!
- brandonwamboldt 9y agoIt's not up to par with Chrome Dev Tools, but something to keep an eye on is https://github.com/devtools-html/debugger.html https://github.com/devtools-html/debugger.html (a project run by Mozilla). This has the benefits of being open source and very accessible to developers (because of the technologies & being on GitHub). It may one day give Chrome a run for it's money.
- eterm 9y agoFor a long time I've used firefox dev edition because their developer tools have been easier, particularly for editing and re-sending HTTP requests. (Right click "edit and resend" in firefox vs ? in chrome). Also in firefox you can screenshot not just the whole page below the fold but screenshot any element by right-clicking the element in the elements pane.
- pluma 9y agoThere is no better alternative. Or at least there wasn't earlier this year. I tested several cross-platform browsers in Q1 this year and I always had to go back to Chrome because it's the smoothest dev experience.
- nailer 9y agoEdge will probably get time travel debugging first, allowing you to rewind and inspect after something happens. Way better than adding debugger or console.log() everywhere.
- grahamperich 9y agowow, that sounds like the holy grail of javascript debugging
- nailer 9y agoYep. It's already in Chakra (MS's JS engine), they just need to do the Edge DevTools support.