In terms of browsers, I have moved back to Firefox from Google for my personal/professional browsing, but I have a product that is heavily reliant on Puppeteer and CDP. There are moves towards interoperability in Firefox, but that's my current blocker.
Firefox DevTools member here. We are looking into Puppeteer/CDP – what is the product you depend on? If you can't post it here, feel free to email me [nickname] at mozilla org
Not the OP but, I use puppeteer (and headless Chromium) as a PDF rendering service. I'd love to be able to try the same thing with a headless Gecko/Slimer.js type thing. My current build process is a major pain to keep updated (building an Alpine docker image with the right version of Chrome to match the right version of puppeteer with the right version of nodejs) And after all that, it's pretty slow.
Badly worded on my part, but it's my own product. I use Puppeteer to run headless Chrome instances in AWS Lambda to evaluate the network traffic associated with advertising data collection. I have a toolchain built around Puppeteer and CDP, which is in use by customers, so migration isn't a viable option for me.
(WebDriver standard contributor and member of the team working on this in Gecko)
There is a plan to update the WebDriver standard to encompass the automation features that are currently only available via devtools protocols. There's agreement it should be possible to open up a bidirectional channel to the browser from within devtools and use it for things like listening to events, streaming logs, etc. However as so often happens reality dictates that implementing something compatible with CDP is needed today in order to interop with the range of existing tooling that's either CDP-only (e.g. Puppeteer) or WebDriver-with-CDP-extensions (e.g. SauceLabs, various WebDriver clients).
In the long term we hope that we end up with a "WebDriver 2.0" that will satisfy all the common use cases in a standard way. That bidirectional protocol will probably end up looking a lot like CDP just to ease the migration for existing implementations, but the details depend on work that hasn't yet been done.
