3 ms·
Some of those updates are to catch up to Chrome's developer tools. If I were in charge of Firefox, I would honestly have them hire a developer or two to focus s
by giancarlostoro 7y ago
Some of those updates are to catch up to Chrome's developer tools. If I were in charge of Firefox, I would honestly have them hire a developer or two to focus solely on the Developer Tools. I'm sure there's many things that browser developer tools could do that we have not even scratched the surface of. I prefer Firefox overall, only use Chrome due to manager only looking at my work on Chrome (it will be deployed in a WebKit container). The DOM Breakpoint feature is one I found out this week about in Chrome, glad it's now in Firefox.
- bzbarsky 7y agoFirefox has an entire team dedicated to developer tools, fwiw. I'm not sure whether your suggestion was "one or two more, in addition to the 7 or 8 already working on it", or "one or two more, instead of the 0 working on it now"...
- giancarlostoro 7y agoI'd happily add more people to the mix yeah, had no concept of how many were working on it currently though, I assumed some people worked on it but not dedicated. As I wrote my comment I realized that kind of tooling is not necessarily easy to work on potentially.
- Vinnl 7y agoThey spent the past few years rewriting them to allow them to build on it more quickly and encourage outside contributions. They finished that a while ago and have been ramping up new features quickly, and some exciting things are coming. For example: https://gist.github.com/jasonLaster/1e220992c294a571dd9b59abd084ccf2 https://gist.github.com/jasonLaster/1e220992c294a571dd9b59ab...
- giancarlostoro 7y agoWoah! Awesome! If I remember correctly the formal name for this is "Event Sourcing."