Safari continues to have the best developer tools, so long as you don't need to debug JavaScript.

aaronbrethorst 12 hours ago | parent | next [-]

I use Safari for day-to-day web browsing and Chrome for development. Feels like the best of both worlds to me.

	▲	matwood 11 hours ago \| parent [-]
		Same. Chrome dev tools, especially around JS are just better.

▲

akst 13 hours ago | parent | prev | next [-]

I don't think JS debugging in Safari is that bad.

But I also use it as my main browser, so maybe there are some nicer features in other browser dev tools I haven't been exposed too.

▲

etchalon 13 hours ago | parent | next [-]

It's mostly that there's no way for third-party tooling to initiate a debugging session, I believe.

	▲	akst 13 hours ago \| parent [-]
		That's fair.

▲

baxuz 12 hours ago | parent | prev [-]

It's criminally bad. You can't copy logged variables. You can't inspect worker threads (!?). WASM support is practically non-existant. You can't even do a heap snapshot on demand, something that should be a basic feature.

The timelines view is practically obfuscated with pretty graphs that show some aggregated data and some automatically generated snapshot points where the dev tools decide that are meaningful.

Inspecting the rendering pipeline is impossible. You can't see memory usage, compositing reasons, long frames (you kinda can but it's tricky)...

Not even going into remote debugging for iOS which crashes either the dev tools or Safari on iOS in any non-trivial scenario — the exact ones you need a debugger for.

▲

boxed 12 hours ago | parent | prev | next [-]

The Chrome tool where you can edit CSS inside the inspect panel and it writes it to the CSS file is amazing and I really miss that in Safari.

▲

troupo 11 hours ago | parent | prev [-]

Safari's dev tools are ... just bad. They are frustratingly cumbersome to use: https://x.com/dmitriid/status/1711701552082079764