Thanks! Yeah, the browser runtime team is doing incredible work to make this possible, backend has made great progress speeding up requests and improving scaling, and us frontend folks are getting to build on top of that.
We're not currently doing active dev work on the FF fork due to the focus on Chromium, and I think the goal is to fully try to move over to Chromium as the user recording browser. So, we probably _won't_ be maintaining the FF fork going forward due to limited resources. I think our next runtime focus after Chromium parity will be Node. We've already got an alpha-level Node for Linux fork that actually works decently - I've used it myself to record Jest or Vitest tests or Node scripts, and debug them. But that does need a lot of work to flesh it out.
We're not currently doing active dev work on the FF fork due to the focus on Chromium, and I think the goal is to fully try to move over to Chromium as the user recording browser. So, we probably _won't_ be maintaining the FF fork going forward due to limited resources. I think our next runtime focus after Chromium parity will be Node. We've already got an alpha-level Node for Linux fork that actually works decently - I've used it myself to record Jest or Vitest tests or Node scripts, and debug them. But that does need a lot of work to flesh it out.