Live data from Hacker News

For developers, Safari is crap and outdated

blog.perrysun.com

141–150 of 623 posts

Re: For developers, Safari is crap and outdated

#141
Of course its crap and outdate... it's the bait to say "we have a browser so you can use that instead of the app store" while knowing that it's a dated, subpar, slow garbage option.

If they cared about having an alternative browser or a good experience, they'd let Chrome run without being hamstrung by webkit.

Re: For developers, Safari is crap and outdated

#142
post #34

Earlier quoted context omitted.

You’re talking as if the W3C or even Mozilla don’t exist. This isn’t an Apple vs Google thing. This is an Apple vs web standards thing. That’s why Safari is outdated for developers.

This isn’t an Apple vs Google thing. This is an Apple vs web standards thing. It’s actually and Apple vs. APIs and technologies that allow fingerprinting on the web thing. Nobody mentions that Mozilla has sided with Apple much of the time to not implement some of these same APIs and technologies.

Then apple should focus on improving the APIs to be privacy safe (how they successfully do in their own APIs). But they are not.

It is not about privacy. It is about revenue.

Re: For developers, Safari is crap and outdated

#143

> Because IE was seriously outdated, lacking support for cutting-edge web APIs and technologies enabling the modern websites and web apps we use today. This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. The biggest problem with IE was all the insanely weird shit it did, not missing features. It would “fix” missing tags, that would then be broken on ev…

I call Safari the new IE because like IE, Safari requires specific code and workarounds for itself quite often. Unlike Chrome or Firefox.

You also need an iOs device and a Mac to debug Safari, like you did need a windows computer to debug IE.

Re: For developers, Safari is crap and outdated

#144
post #58
post #23

Earlier quoted context omitted.

The last thing I’d want is a web push notification. I don’t have a favorite browser, but if there were one which blocked pop-ups asking me to assent to notifications, it would be my new favorite.

Web push notifications would only apply to PWA's, which you have to deliberately install by seeking out the add to home screen menu item. They are not the nuisance you are making them out to be.

[deleted]

Re: For developers, Safari is crap and outdated

#145

Speaking from personal experience as a developer (although YMMV) - this is totally true. And I'm not even talking about some newfangled APIs like WebUSB and such (I don't really care about those personally). Safari's handling of regular HTML + CSS is regularly broken compared to other browsers. (At least in my experience.) Open the site in Chromium. Yep it works. Open the site in Firefox. Yep it works. Open the site…

Open the site in Chromium. Yep it works. Open the site in Firefox. Yep it works. Open the site in Safari. Ugh... it's broken.

This is unacceptable from professional developers. Progressive enhancement is a thing.

Apple announced at last year’s WWDC (https://developer.apple.com/wwdc20/10663) the areas where they improved interoperability with other browsers and that Safari passed 140,000 interoperability tests:

We made a really big effort this year to improve Safari's interoperability with other browsers. One way to measure that is web platform tests. It's a set of tests used by browser makers to ensure interoperability, so your web content operates the way you expect across browsers. So I'm pleased to announce improved interoperability for service workers, XHR + Fetch, pointer events, CSS, SVG, web assembly, and many more areas. Safari passes a hundred and forty thousand new interoperability test cases this year.

And you can look forward to continued progress in this area.

Re: For developers, Safari is crap and outdated

#146
post #22

Apple has its own opinions about what web standards it should implement. It’s as simple as that. Google has been extremely successful in convincing developers that browsers that don’t behave like Chrome are behaving wrong. Don’t get me wrong, I wish Safari had more features, fewer bugs, and an evergreen release cycle. It’s clear Apple do not see themselves as competing with Chrome, largely because of iOS, and I do wa…

Apple's opinions are simple: If they have a good browser, then the app store - their cash cow - becomes unneeded.

Re: For developers, Safari is crap and outdated

#147
post #137

Earlier quoted context omitted.

At the time IE 6 was released, it was the best browser available. The problem was Microsoft acted is they had “won” and stopped updating it for years, where it calcified and became the hot mess we all knew and disliked.

That I never got. You are a market leader and you just stop whatever you are doing? How did that happen? Arguably the biggest mistake of MS.

IE6 was wrapping up development when the US government sued to break up the whole company for giving it away with Windows. Perhaps not a coincidence they stopped work then?

Re: For developers, Safari is crap and outdated

#148

> Progressive web apps I don't want PWAs. Apparently Google is their biggest promoter and Chrome has the best PWA support but the apps still stuck. I prefer to leave them open in a Chrome tab than have it pop out and pretend to be a native app. So good on Safari to not support it properly, it does not provide any benefit at all. > Lagging support for WebRTC and other features Again, I don't care. Just write a native…

> Again, I don't care. Just write a native app if you want to do video/audio calls, or send/receive files. The worst native app for these purposes is better than the best WebRTC implementation.

Google Meet and Jitsi are fantastic, in my opinion. Zoom however has had a constant parade of vulnerabilities over the last year.

Re: For developers, Safari is crap and outdated

#149
post #137

Earlier quoted context omitted.

At the time IE 6 was released, it was the best browser available. The problem was Microsoft acted is they had “won” and stopped updating it for years, where it calcified and became the hot mess we all knew and disliked.

That I never got. You are a market leader and you just stop whatever you are doing? How did that happen? Arguably the biggest mistake of MS.

At the time, and perhaps still today but greatly lessened, Microsoft was used to both becoming the victor by crushing the opposition and then staying the victor because no one dared take a second swing. Anyone else who thought about challenging usually thought against and then went and carved out a quiet niche elsewhere.

Besides, nobody got promoted at Microsoft for staying the course and making incremental improvements. Once there were no more balls to be knocked out of the park, developers moved elsewhere to buff up reviews and get bullet points for major projects.

Re: For developers, Safari is crap and outdated

#150

Earlier quoted context omitted.

>This is just false, or at best only half of the story to make a false equivalence. IE was cutting edge until Firefox. After developing during the IE 5.5/6 years there's no way I'm giving you a pass in calling IE cutting edge.

At the time IE 6 was released, it was the best browser available. The problem was Microsoft acted is they had “won” and stopped updating it for years, where it calcified and became the hot mess we all knew and disliked.

From what I've heard, MS's whole idea was that ultimately, "the web" was broadly going to be scrapped. What people were actually going to be using, "in a few years", was going to still be IE, but the webpage would just be a thin wrapper that would load in ActiveX controls delivering actual windows apps, in the browser.

Apparently they got close enough to getting this working that a bunch of South Korean banks and such bought into it heavily, which meant you could only do online banking in that country, for a while, on either a windows phone or an actual windows machine.

However, they narrowly missed getting developer buy-in on that stateside, before the whole "XMLHttpRequest" thing went crazy, and we started building javascript apps for everything.

Post reply on HN