Yeah it's pretty good, but it still has issues. My game uses a manifest.cache and the console/networking tab does not give good feedback with it. In chrome, the console will tell me, "This file could not be found". In Firefox, it gives me no feedback that was a problem... things just don't work as expected.
Also, I'm pretty convinced the dev tools have some sort of memory leak in them. Every 3-5 days I have to restart Firefox or my game runs so slow it's unplayable. I don't think it has to do with my code because I've got no persistent store and refreshing the page doesn't fix it. Restarting the browser always does.
Sometimes the debugger gets confused and puts breakpoints on things I no longer have breakpoints on.
The profiler does not have a very useful view. I can't figure out how to delete reports I've made without closing the dev tools. More importantly, I can't find a convenient way to answer the question, "What are the slowest parts of this code?" I have to do a lot of manual labor expanding deeply nested trees.
As I said, it's pretty good. These are just things I'd like to see improved, not things that drive me crazy. I prefer the dev tools to firebug because firebug takes a relatively long time to start up.
Re: this update, I'm embarrassed to say I didn't know console.error even existed (I don't consider myself a JS expert). I've been using `throw new Error("message")`. Will that show stack traces now, too? I always have to put breakpoints on the line with the throw to figure out the call stack. This can add a lot of time to my debugging if I'm not sure how to reproduce the error.
Also, I'm pretty convinced the dev tools have some sort of memory leak in them. Every 3-5 days I have to restart Firefox or my game runs so slow it's unplayable. I don't think it has to do with my code because I've got no persistent store and refreshing the page doesn't fix it. Restarting the browser always does.
Sometimes the debugger gets confused and puts breakpoints on things I no longer have breakpoints on.
The profiler does not have a very useful view. I can't figure out how to delete reports I've made without closing the dev tools. More importantly, I can't find a convenient way to answer the question, "What are the slowest parts of this code?" I have to do a lot of manual labor expanding deeply nested trees.
As I said, it's pretty good. These are just things I'd like to see improved, not things that drive me crazy. I prefer the dev tools to firebug because firebug takes a relatively long time to start up.
Re: this update, I'm embarrassed to say I didn't know console.error even existed (I don't consider myself a JS expert). I've been using `throw new Error("message")`. Will that show stack traces now, too? I always have to put breakpoints on the line with the throw to figure out the call stack. This can add a lot of time to my debugging if I'm not sure how to reproduce the error.