36 points | by feross 7 hours ago ago
8 comments
It's so good to see Safari steadily making progress on being a decent browser.
Safari continues to have the best developer tools, so long as you don't need to debug JavaScript.
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.
I use Safari for day-to-day web browsing and Chrome for development. Feels like the best of both worlds to me.
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.
It's mostly that there's no way for third-party tooling to initiate a debugging session, I believe.
That's fair.
It's criminally bad. You can't copy logged variables. You can't inspect worker threads (!?). WASM support is laughable. You can't even do a heap snapshot on demand.
It's so good to see Safari steadily making progress on being a decent browser.
Safari continues to have the best developer tools, so long as you don't need to debug JavaScript.
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.
I use Safari for day-to-day web browsing and Chrome for development. Feels like the best of both worlds to me.
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.
It's mostly that there's no way for third-party tooling to initiate a debugging session, I believe.
That's fair.
It's criminally bad. You can't copy logged variables. You can't inspect worker threads (!?). WASM support is laughable. You can't even do a heap snapshot on demand.