Can it inspect WebSockets frames yet? I'm a Firefox user but I miss that sometimes when developing stuff.

I heard that this was going to be a GSOC project this summer, but I'm not sure if that was approved or not.

Mozilla methodology: staffs should avoid well defined works so that volunteers, interns, and students can do them.

It’s not a bad strategy: just figuring out what to do can be much harder than getting it done (which can be more easily delegated). Architects (of old) made the big bucks in the days; now according to the google model they’ve all become senior engineers and the definition of and piecing off of work is much less formal (not to mention that it might go out to interns or the community rather the junior devs).

I can also picture it organically happening: if I were a core dev, would I focus on the issues "anyone" could pick up, or the ones that only someone as deeply invested into the code base as me would have any hope of untangling?

Firefox is not their primary product and they have no competition. /S

Oh... I consider Mozilla methodology a good methodology. Staffs probably can do both well and ill defined works better than volunteers, but they do have comparative advantage in ill defined works. A problem with methodology is that well defined works can be delayed, but Mozilla do have massive contributor pool so that it is not usually a problem.

It was, here's the bug: https://bugzilla.mozilla.org/show_bug.cgi?id=885508

This is the big one that sends me back to Chrome every time I start to get settled in Firefox.

Looks like they finally added resizable columns in the networks tab! https://bugzilla.mozilla.org/show_bug.cgi?id=1358414

As much as I like a Firefox, no inline/live editing of Javascript leaves things a bit frustratingly behind the curve. Even Edge Classic has that, and it's terrible.

Those have worked for a while now? Like https://umaar.com/dev-tips/129-inline-breakpoints/

The bigger issue is when local variables aren't captured by the context when paused in chrome. I'm curious how the Firefox devtools handle that.

We (Chrome DevTools) have had inline breakpoints since at least January 2017: https://umaar.com/dev-tips/129-inline-breakpoints/

The human-friendly variable mapping is very interesting, though. We'd love feedback on how well it works out in the wild.

Happy to discuss collaborating on mapping variables. The current approach is based on re-parsing with babel, but we would like to extend source maps to include relevant mapping data.

https://twitter.com/auchenberg/status/1129435519727820800