Re:New Performance Tools in Firefox Developer Edition 40
by seanp2k2 on Tuesday June 02, 2015 @11:38PM
(#9650428)
How about...open everything in Atom instead, so you can use what you're used to (or vim / emacs / ST / whatever), and have that be able to e.g. Set break points and inspect stacks? Separate the IDE from the browser so they can each evolve faster. Give and API to interact with the browser so anything can integrate with it.
[ Parent
| on HN ]
Re:New Performance Tools in Firefox Developer Edition 40
by Excavator on Wednesday June 03, 2015 @12:03PM
(#9653523)
You already have an API in the remote debugging interface:
https://hacks.mozilla.org/2013/03/firefox-developer-tools-wo...
Re:New Performance Tools in Firefox Developer Edition 40
by EdSharkey on Wednesday June 03, 2015 @02:18AM
(#9650848)
Intriguing! If I ever get into an extended debugging session, I might try it.
I try to TDD my code (or at least write lots of tests to dig myself out of the hole), so I don't find myself doing heavy breakpoint debugging as much these days.