top | item 27144285

(no title)

godman_8 | 4 years ago

Hopefully with Microsoft's aggressive updating policies in Win10 old Edge will be killed off soon. We'll be sitting pretty when it comes to web standards. Safari lags behind but not by much.

discuss

pjerem|4 years ago

In our team, every time there was a bug in Safari, it was something awfully wrong in our code that just happened to work on Chrome/FF for mysterious reasons. I never had a problem on Safari with standard quality code.

slaymaker1907|4 years ago

This is being far too kind to Safari. They were the ones who unilaterally decided that 7 days is sufficient time to clear out localStorage and IndexedDB.

Additionally, found this recent post going into why Safari is hot garbage. https://infrequently.org/2021/04/progress-delayed/

While the File System Access API is still being developed, I'm not holding my breath for it to appear on iOS. To be fair, it isn't supported yet on mobile Chrome (for Android obviously), but I expect it will be added quickly after the v1 of the API is finalized. I expect it will either never appear on iOS or it will take 5+ years from now...

edoceo|4 years ago

HTML5 date and time inputs still don't work on Safari tho.

yjftsjthsd-h|4 years ago

> We'll be sitting pretty when it comes to web standards.

You'll be sitting pretty on standards, or you'll be able to just target Chrome and forget about standards?

kungito|4 years ago

Exactly, what a ridiculous statement from GP. Now it seems like the web might end up in webgl canvases anyways

babypuncher|4 years ago

Apple should ditch WebKit and adopt Gecko. Mozilla could use the funding. and the two organizations share similar philosophies on user privacy. It would also deal a significant blow to the growing Blink monoculture.

diegof79|4 years ago

According to the book “Creative Selection” (by one of the original Safari devs). They tried with Gecko first, but the POC didn’t went far: the build system at that time was messy and they couldn’t get it work. So they switched to KHTML, because of the nice code base. That internal fork evolved to WebKit.

stephenr|4 years ago

By that logic Firefox should drop gecko and adopt WebKit. It’s already maintained by a megacorp and isn’t blink.

sonthonax|4 years ago

Why should they? WebKit was developed by Apple, and is deeply integrated in the OS.

atatatat|4 years ago

Apple probably has no interest in throwing good money after bad, with regards to security work involved in making that feasible.

addicted|4 years ago

The major difference was MS aggressively pushing against IE11.

It really gives management no opportunity to stand still on this anymore.