Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

For developers, Safari is crap and outdated

blog.perrysun.com

Post reply on HN
Print view View original

111–120 of 623 posts

Re: For developers, Safari is crap and outdated

#111

Post by upbeat_general »

vorador wrote: post #64
afavour wrote: post #50

Earlier quoted context omitted.

In what way can PWAs be abused?

Sorry, I'm using the OPs parlance here – by PWA I think he means "JS apps that use advanced browser APIs". The typical concern is that a phisher will use to make a page that looks like Google's sign-in page and display it in fullscreen mode. This would let them collect credentials while mirroring the input in a real form that'd be filled in the background.

How is that related to the APIs being talked about? What advanced browser APIs does phishing in full screen require?

The new iOS 15 safari is full screen (and you’ve always been able to add to home screen to make a website really fullscreen)…

Re: For developers, Safari is crap and outdated

#112

Post by pupppet »

rubyn00bie wrote: post #18

> 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…

>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.

Re: For developers, Safari is crap and outdated

#114

Post by upbeat_general »

diebeforei485 wrote: post #16

Yes, because we all want notifications and more things running in the background that can access to the device's ports. I take the points about not supporting CSS features and some of the other web standards, and the issues around Apple's 30% cut, and I'd add that some of Apple's censorship (eg. banning Parler for a while, asking Telegram and Tumblr to not allow access to certain content) is troubling, but I don't th…

The thing is sites can already do this on chrome (desktop and android) and it hasn’t caused any widespread issues to my knowledge.

Why would adding it to Safari have a different effect? Plus iOS is improving on its notification suppression and its relatively trivial to suppress notifications that aren’t interacted with after some limit.

Re: For developers, Safari is crap and outdated

#115

Post by zarzavat »

andrewmcwatters wrote: post #87
rubyn00bie wrote: post #18

> 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…

Thank you. I have no idea what these people are talking about. They obviously didn't actually do development back then. > Apple took years to finally add WebRTC support to Safari, far enough behind Chrome and Firefox that it practically became a running joke among developers and even industry observers. Really? Because no one I know uses WebRTC and would rather use ffmpeg and sockets to do serious work like that over…

When people say that Safari is like IE they aren't talking about 20 years ago when IE was dominant in its prime, they are talking about the geriatric IE era when it was an also-ran that you had to support but didn't implement modern features such as flexbox properly etc.

Re: For developers, Safari is crap and outdated

#116

Post by roca »

andrewmcwatters wrote: post #106
roca wrote: post #97

Earlier quoted context omitted.

Lots of sites use WebRTC for video and audio calls. Google Meet, Discord, Slack for example. On desktop it's far more secure to use those in-browser than via desktop apps.

Yeah, and those all suck up my RAM. Color me nonplussed that WebKit doesn't follow in Chromium's footsteps.

Feel free to not use those apps. But a lot of people do want to use them.

Re: For developers, Safari is crap and outdated

#117

Post by [deleted] »

andrewmcwatters wrote: post #106
roca wrote: post #97

Earlier quoted context omitted.

Lots of sites use WebRTC for video and audio calls. Google Meet, Discord, Slack for example. On desktop it's far more secure to use those in-browser than via desktop apps.

Yeah, and those all suck up my RAM. Color me nonplussed that WebKit doesn't follow in Chromium's footsteps.

[deleted]

Re: For developers, Safari is crap and outdated

#118

Post by skhr0680 »

pupppet wrote: post #112
rubyn00bie wrote: post #18

> 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…

>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.

IE was the blunt and dangerous cutting edge because you haven't thought to buy a new knife yet

Re: For developers, Safari is crap and outdated

#120

Post by alwillis »

pupppet wrote: post #112
rubyn00bie wrote: post #18

> 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…

>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.
Post reply on HN