CDP is a good exmaple of why the ecosystem has converged around Chrome and not Firefox. CDP has:

- Full documentation

- A stable API

- Tooling like this

Firefox has none of that: implementing the firefox devtools protocol means reverse engineering it, and then sometimes it still breaks when Firefox updates!

▲

Un1corn 4 hours ago | parent | next [-]

I haven't used the devtools protocol of Firefox but CDP is one of the worst protocols I had to work with. Everything is "experimental", inconsistencies between different domains, multiple ways to do some stuff and revealing internal stuff.

	▲	kg 5 minutes ago \| parent \| next [-]
		Seconding this, I've used CDP directly to solve problems and it's a horrible protocol with a really buggy implementation. The documentation is pretty sparse and the implementation is inconsistent with the documentation sometimes. It's true that if you want to know what a method is named and which parameters it takes you can find that out, but I rarely found the answers I actually needed to use things correctly.
	▲	walls an hour ago \| parent \| prev [-]
		Yep, in certain cases requests/responses will only show up in the Fetch domain, sometimes only in the Network domain, and sometimes neither!

▲

cxr 3 hours ago | parent | prev | next [-]

A recent attempt to bring up an element in Firefox's inspector by right-clicking the element and selecting the appropriate menu item resulted in the fans on my machine spinning up and the process needing to be killed after it appeared to hang and started chewing through RAM. All in response to my attempt to get a relatively simple view of the DOM tree on the screen to interact with.

When I tried it again I observed an increase of 130MB RAM to bring up the initial window/view, along with noticeable lag to put its contents on screen and make the controls interactive. When I collapsed all the nodes so that the only nodes in the tree toggled open were the HTML body element and its ancestors, it ended up consuming 400MB more—to collapse tree nodes and show fewer things on the screen.

That's half a gigabyte to bring up a less usable tool than the original DOM Inspector that Joe Hewitt checked in to the mozilla.org CVS server back in 2001.

The fact that Firefox's devtools team has ignored the readily available information and guidance from Firefox's own repo about how to do large JS codebases because they instead favor doing a wholesale import all of the bad practices from the NodeJS/NPM world is a serious problem unto itself.

▲

googlywoogly 3 hours ago | parent | prev [-]

Chrome's/Google's attack on adblockers is why 'the ecosystem' now shifting away from chrome to firefox

▲

surajrmal 2 hours ago | parent [-]

Except it's not. HN users aren't representative and all trackers show no discernable uplift of Firefox usage since manifest v3. There also exists chromium based browsers with continued v2 support.

	▲	yjftsjthsd-h 2 hours ago \| parent [-]
		> and all trackers show no discernable uplift of Firefox usage since manifest v3. The browser that goes out of its way to protect user privacy against trackers doesn't show up in trackers. This is neither surprising nor particularly damning.