As others have pointed out, it may be worth looking into whether or not your reasons for using Chromium for the devtools are simply habit.
Speaking for myself, I'm in the other camp. I never really ditched Firefox for Chrome except for a brief period[0]. I returned to Firefox back when it was still called "Firefox (Not Responding)". Other than the renaming (/s), it -- generally -- flies. The devtools do what I need them to do, however, I used to hop back and forth from Chromium to FF a lot more.
So I'll be re-evaluating things, again, myself -- just in the other direction. :)
[0] I used Chrome for about two years after its release because Firefox wouldn't work with an internal application. It was just easier to use a single browser.
Speaking for myself, I'm in the other camp. I never really ditched Firefox for Chrome except for a brief period[0]. I returned to Firefox back when it was still called "Firefox (Not Responding)". Other than the renaming (/s), it -- generally -- flies. The devtools do what I need them to do, however, I used to hop back and forth from Chromium to FF a lot more.
So I'll be re-evaluating things, again, myself -- just in the other direction. :)
[0] I used Chrome for about two years after its release because Firefox wouldn't work with an internal application. It was just easier to use a single browser.