you didn't get the point of what i was trying to say. I do check what i make on safari, but what i am saying is that most of the developers code using chrome or firefox, and not because safari is a bad browser, but because safaris dev tools are miles behind chrome or firefox, you can't fix a browser if devs are not using it, i bet 99% of web developer will recommend you to use chrome or firefox, again not because safari is a bad browser, but because they mainly use chrome/firefox, and again - because dev tools are way superior, and why should they use safari if it is much more painful to develop than simply using chrome. Same happened to IE, it was a paint to develop and even bigger pain to debug, firefox firebug was released and the job got multiple times less painful. For me this safari is bad thing is so simple to solve - IMPROVE DEV TOOLS TO ATTRACT DEVS, the rest will come.
Good for you, bad for web developers!
You are a web developer? Seems not. Stick to the standard and choose firefox or chromium. Or you stick to safari. But then you need a Mac. A old Mac. With an old Safari. Not updated. People use it. Safari 10-9. It remembers me to internet explorer, safari/apple is not better
And at that point, a number of devs will start relying on quirks of that renderer, and users of alternative browsers will struggle even more than they do now.
Because developers suffer. The newest safari is maybe not the problem (except of recent security leaks of version 15), but apple binds the browser tight to the OS version. We could forget the IE/ NETSCAPE past, BUT now we have the old versions of safari! No es6, gliched flexbox. We have to force customers to update the browser.... We are in 2022, do we need this?
margin:-.1 to make it work for safari only. Check Stack overflow #safari-bug. You will find the bad situations. Disclaimer, firefox/chromiium have bugs, every Software do, but they follow the standard
No, he's not. Developing *on* Safari is absolutely a pain and that's on Apple to fix by providing better developer tools. They are just running way to far behind, never mind debugging Safari on iOS. Developing *for* Safari even more so, the feature gap between Safari and the rest of the market is becoming way to large, never mind that features that are implemented aren't always as stable as they should be to be useful in the first place.
You managed to get a PWA running on safari with all the features? If not, step on the break and wait until the web is progressing for apple/safari. You do not have to use chrome, check out the open source, no spy version of chrome, chromium, or Firefox. What I hate is the pressure of every consumer of an browser, who does not know the impact of using an browser which is obvious lacking behind, but sees only the "frontpage" with crisp clear Animations and state of the art UX
The web is growing. Experimental does not automatically mean bad as long it get accepted into the standard later on. Don't get me wrong. I'm the last one who would think that competitors hurt the market, but developing for browsers and safari makes it just tiresome. Want to test on safari 12? Tell me how you do
I stay with Safari because of the password management and autofill, but this highy annoying bug has been often noted but never fixed:![]()
You know that makes Chrome the new IE right? Please tell me you understand that.
Yes, that makes Chrome the new IE. And, until I see an example of a large number of websites that load fine in Safari but fails in chrome, that’s the reality of the matter. Fortunately for me, the sites I need to visit are adhering to web standards, not chrome standards.
It's not helping that Google forced all Android OEMs to preload Chrome if they want GMS and Android certification. The war is on mobile, and Chrome is simply holding that market.
I mean, Safari is the only browser on iOS, so...
