3 comments

  • gabeidx 1 hour ago
    It's so good to see Safari steadily making progress on being a decent browser.
    • jen729w 9 minutes ago
      I guess the snark is funny, so I'll bite.

      I've used Safari daily for … must be 20 years now? Every day, for everything, minus the odd exceptionally rare circumstance. And I couldn't tell you what the last one of those was, it was so long ago.

      I'm a web developer. I use its devtools constantly.

      People ask why do you use Safari and not Chrome and I think the question is backwards. Why, given how lovely Safari is, would you go and download Chrome? It's really ugly and doesn't look like any of the other apps on my Mac.

      When I do want other devtools, I vastly prefer Firefox's to Chrome's.

  • etchalon 2 hours ago
    Safari continues to have the best developer tools, so long as you don't need to debug JavaScript.
    • aaronbrethorst 1 hour ago
      I use Safari for day-to-day web browsing and Chrome for development. Feels like the best of both worlds to me.
      • matwood 17 minutes ago
        Same. Chrome dev tools, especially around JS are just better.
    • akst 1 hour ago
      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 1 hour ago
        It's mostly that there's no way for third-party tooling to initiate a debugging session, I believe.
        • akst 1 hour ago
          That's fair.
      • baxuz 1 hour ago
        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.
    • boxed 28 minutes ago
      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.