This

I have users that have issues with Safari, CSS and Javascripts ones.

I MUST own an Apple device to debug anything.

I'm sorry but as a Free Software Web Developer I can't spend 2K€ on a Mac to just fix a CSS issue.

I agree with you on this one, I've never understood the fascination with Chrome. Safari has done a pretty good job of maintaining a clean and simple UI along with being reliable.

If there was a downside I guess it would be in the realm of extensions/plugins where Chrome probably has a leg up. That's where I decided to make the jump to Brave. All the same Chrome extensions without the Google nonsense (and built in ad blocker).

I still really like Safari though and would likely use it daily if it had a built-in ad blocker.

I'll join in saying I also daily Safari for generale usage (with only two extensions installed 1Blocker and Are.na) and I have basically zero issues.

I also do dev work in Firefox + Safari. I use Firefox mainly because I prefer their dev tools to do frontend work. Chrome I almost never use. This insistence that Safari is the new IE is honestly baffling. Yes Safari is not perfect and yes Apple is Apple. Still, Safari is far from being a train wreck.

> why do you use Safari and not Chrome

To me, it's annoying people ask that question. It's like they ask why I use brand A of shoes and not B, but it's my choice and nobody would expect a monopoly from an Ad company to be a good thing.

Social pressure is real, though.

I find Safari's devtools to be quite annoying, but to each their own. Firefox' dev tools still hold the crown for me.

The lack of cross-platform support is also annoying to the point where I generally don't bother testing on Safari unless I'm absolutely forced to. Until Apple releases a Safari build for Windows and/or Linux, Safari users will just have to rely on Safari's compatibility with cross-platform browsers.

The open source version of WebKit works fine as a user, but behaves differently from any official Safari releases, so as a web developer it's not really usable as a testing tool.

The reason to use Chrome is better extension support, better/more useful functionalities (translation, favicon bookmarks, Google Lens), better autofill/autologin, and better performance for web apps generally. Another very useful property is being able to sync your Chrome profile on any computer, which comes in very handy when you need to do stuff on computers you do not own. Doing the same with Safari is possible but a hassle.

I have used Safari since it replace Internet Explorer back in the days, then switched to Chrome a few years ago after a beta broke password syncing and AdBlocker Extensions for Safari were paid/not as good.

Like much of Apple's software, it has strengths and looks good but is really lacking in many ways. It also locks you into the walled garden pretty tight, which can be annoying at times.

Apple should go back to releasing a cross-platform version if they want to be taken seriously, in my opinion. In general, their incentive to build software solely for their platform is a double-edged sword because they can't manage to create hardware that can cover every need (especially for 3D/engineering), and it becomes very annoying to rely on it the moment you need to use another OS (either Windows or Linux).

Another example is Apple Notes being decent, but using it in the web browser is basically a joke (might as well not exist).

I also use Safari as my main browser, but do have some gripes.

The one that bites me every day is how I cannot pick an arbitrary search engine. The ones they have are very few and awful.

One that bites me on occasion is the inability to selectively disable JavaScript per website.

Another is the atrocious permissions management for extensions. On iOS you can’t even deny access to a specific website until you allow it once first.

One that bites me rarely is AppleScript support being slightly worse than in Chromium, specifically there being no way (other than GUI automation) to make a new Private Window.

One that hasn’t bitten me yet is the ugly pill-shaped tabs in Tahoe, together with the removal of the unified tab layout.

The most frustrating part is these are very easy to fix. Note also that this isn’t an endorsement of Chromium, there’s a reason those browsers aren’t my main. Right now there isn’t a single web browser I like and that does everything I want acceptably. But Safari is the least bad.

Safari's dev tools are infuriatingly cumbersome in comparison to Chrome. They go out of their way to make even the simplest actions hidden in multiple selects and popup menus. I even made a screencast of it: https://x.com/dmitriid/status/1711701552082079764

As a browser? I agree with you.

I don’t think the common question is “Why not use Chrome instead of Safari?” but “Why use Safari?”

This is like being in the 2000s and saying "Why would I use anything but IE5, everything works with it"

The market share is what makes those circumstances exceptionally rare. Meanwhile we're having to use safari specific fixes and refrain from using he newest standards just because of safari

As a web dev, Safari is like the new IE6 - it does everything slightly wrong and I have to sprinkle my code with special cases for it because too many people use it to ignore. This modal scrolls properly in Firefox and Chrome? Not Safari, better add a million extra css attributes and maybe even some JS for fun to deal with it. This CSS parses exactly the same in Firefox and Chrome? Not Safari, they decided to Think Different. My workplace's frontend codebase is absolutely polluted with /* Safari fix: ... */

https://www.google.com/search?q=examples%20of%20code%20that%...

This is probably the single most frustrating issue on iOS Safari, and the Reddit website triggers it all the time.

It would be nice if Reddit wasn't a total hog that could barely load two separate pages without crashing from a memory leak, or allow you to navigate without breaking the back button completely, but it'd also be nice if Safari was more resilient to it.

Same. Chrome dev tools, especially around JS are just better.

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

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.