What are you missing? I was feared of this too, but they seem to be just fine.
Can't inspect websocket frames. It's ridiculous.
I'm out of that, but maybe somebody else in here got an idea how to fix your problem with that.
My solution is to use chrome when faced with that particular limitation. There's a bug open on the mozilla tracker and it's been there for a while but no one seems to care.
While I run into this too from time to time, it's not something everyone uses. Also it takes me 5 seconds to workaround by debug logging incoming ws messages. Most web devs I talk to can do everything with FF devtools more than fine.
I use both, Chrome for client side dev, Firefox for everything else. Chrome is just the dev tool. Works like a charm because switching between tabs inside a browser is just as quick as alt-tabbing between browsers.
I use them all the time, don't seem clunky to me. What else is not working other than the websockets inspection you mentioned?