One practical challenge across all these protocols and frameworks is detection. Modern websites often fingerprint automated browsers regardless of whether they are controlled via WebDriver, or CDP. At Kameleo, we put a lot of effort into minimizing this risk. When using Kameleo's custom-built browsers like Chroma and Junglefox, these automation frameworks can operate in a much more realistic, undetectable way, even in advanced scraping and automation scenarios. If you are interested, give it a try, if need help: contact me
Great breakdown of the BiDi transition. The WebSocket bidirectionality makes so much sense once you see how polling slows down network interception at scale. I've been runnning some tests with Playwright's FireFox handling and the BiDi performance gains over classic are real, especialy for streaming events. Curious how long until BiDi fully replaces CDP for Chromium debug scenarios tho.
One practical challenge across all these protocols and frameworks is detection. Modern websites often fingerprint automated browsers regardless of whether they are controlled via WebDriver, or CDP. At Kameleo, we put a lot of effort into minimizing this risk. When using Kameleo's custom-built browsers like Chroma and Junglefox, these automation frameworks can operate in a much more realistic, undetectable way, even in advanced scraping and automation scenarios. If you are interested, give it a try, if need help: contact me
Yes, detection is surely another important aspect. Thanks for bringing that up!
Great breakdown of the BiDi transition. The WebSocket bidirectionality makes so much sense once you see how polling slows down network interception at scale. I've been runnning some tests with Playwright's FireFox handling and the BiDi performance gains over classic are real, especialy for streaming events. Curious how long until BiDi fully replaces CDP for Chromium debug scenarios tho.
Yes! That's surely interesting to keep an eye on!