In the same vein, but with less idiomatic C, note also https://github.com/hnsl/librcd. I had the opportunity to work with it two years ago at Jumpstarter, and it was quite wonderful.
Note that this bug originally seems to have been called something like "Implement LZMA compression", and the early comments are about that; it's some way in that someone says "oh, and Google have this new Brotli thing which might be even better".
Mozilla can be quite slow with certain features; for example work on U2F support hasn't even begun one year after a ticket was made (https://bugzilla.mozilla.org/show_bug.cgi?id=1065729). I'm not exactly holding my breath.
They've already tried to land the code to add brotli support but had to back it out because of an Android build failure. They're moving pretty quick on this. It helps that they already had brotli for WOFF so there is less review required.
Interesting, you don't have lag when first opening it? I was investigating pretty much the same thing yesterday, in the end my problem was that the JSD was ridiculously slow to toggle, but firebug is already working to move to JSD2 so I can't really complain too much. There is a test extension you can use attached to this bug.
I was getting something like 100ms to pause and 10000ms to unpause. With 5 tabs loaded and a couple hundred tabs unloaded. I disabled the javascript parts of firebug for general use, which does avoid the problem most of the time.
Aha, you're right! Disabling the Script tab helps immensely. It's a shame since I need the Script tab for a lot of work, but it's not too much of a pain to disable/reenable.
Crashes and slowness that vary with Firefox versions is Firefox's fault, and in this case the note about tab switching points pretty clearly to a problem with the debugger service.
Not really, no. There was some talk about adding a Firebug panel to the built-in tools, but nothing has really come from it, and any deeper UI integration is probably out of the question for being too much work. But suggestions about how to make it better are still welcome, of course.
The main thing we have gotten out of the new devtools are new cool APIs, e.g. for debugging, paint flashing, CSS auto-completion, profiling (though we haven't gotten around to using most of them yet).
