3 ms·
That seems to be premature. Depends what you consider a DevTool. Chrome still has far better profiling/tracing tools for performance analysis. The latest Chrome
by cromwellian 13y ago
That seems to be premature. Depends what you consider a DevTool. Chrome still has far better profiling/tracing tools for performance analysis. The latest Chrome versions even let you hover over functions and view what the V8 JIT thought of them (e.g. deoptimized and why). Even relatively low hanging fruit, like debugging WebWorkers is missing from FF. I see tons of missing stuff that Chrome DevTools has that FF is missing. It doesn't have something like the Timeline tab for tracking memory/framerate over time. I don't see stuff like HTML5 FileSystem/IndexDB/localStorage browsing. SourceMap support doesn't match Chrome. Etc.
FF seems to do better with the DOM/Designer portion of tooling, but from a JS-heavy coder perspective it seems behind.
- mnemonik 13y agoLike we aren't working on all those things ;)
- cromwellian 13y agoSometimes I wonder if Chrome and Mozilla could standardize on some DevTool APIs, like JVMs standardized on JVMTI/JPDA, so that a portion of the code could be shared and people could build JS dev-tooling that would work with either browser. Obviously, there's lots of stuff that is tied to internals, especially when it comes to profiling and native code bindings, but it seems like something could be done. A good start would be for JS VMs to adopt a standard debugger protocol so that attaching a tool to the JS debugger would be browser independent.