Mostly in everything that has to do with PWAs. It’s gotten better since they introduced Web Push last year, but there’s still a lot of things it doesn’t support, like Web Bluetooth, AV1 (except for devices with hardware decoders like the 15th gen Pro iPhones), and things like mobile sensor inputs.
But also in how bad its rendering engine is. Things that work on every other platform render super weird in WebKit.
Thanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
Besides rendering bugs that may or may not be Safari’s fault, I wanted to get uBlock Origin on an iPhone but it’s not available, IIRC because the content blocking API is more restrictive than what uBlock is designed for.
I’m telling you my experience as a web developer for the last 20+ years. If you want specific examples, you could look online. I’ll tell you my SVG icons sometimes don’t work in mobile Safari and I have no idea why. They work 100% of the time in every other platform. I also have to do weird things to get the safe viewport measurements to work in my PWA, again, only in mobile Safari.
I’ll tell you what, you try asking customers to go toggle a feature flag and tell me how that works out.
Safari is almost always the last browser to adopt a standard, often times years after it’s been standardized. And don’t tell me it’s because they take their time to get it right, because their rollout of Web Push was atrocious.
OK you’re speaking from a completely different point of view then. I was more curious about what I would be missing out on using Safari right now. Definitely not thinking about how a project I paid somebody to create is going to render.
You’re missing out on the things people can’t create because Safari is holding the industry back. Just because it’s not a user facing problem doesn’t mean you’re not affected as a user.
Mostly in everything that has to do with PWAs. It’s gotten better since they introduced Web Push last year, but there’s still a lot of things it doesn’t support, like Web Bluetooth, AV1 (except for devices with hardware decoders like the 15th gen Pro iPhones), and things like mobile sensor inputs.
But also in how bad its rendering engine is. Things that work on every other platform render super weird in WebKit.
Thanks. Do you have an example of the super weird rendering? Also are none of what you’re saying here togglable in the WebKit Feature Flags to mess around with bleeding edge features?
Every time I want to use a new feature of web browsers, if support stops me from doing so, it’s always safari to blame.
What was that last or current feature you’re missing out on and what’s the use case?
Besides rendering bugs that may or may not be Safari’s fault, I wanted to get uBlock Origin on an iPhone but it’s not available, IIRC because the content blocking API is more restrictive than what uBlock is designed for.
I really can’t remember an example off the top of my head. Over the last 5 years it’s probably been an issue more than 20 times.
I’m telling you my experience as a web developer for the last 20+ years. If you want specific examples, you could look online. I’ll tell you my SVG icons sometimes don’t work in mobile Safari and I have no idea why. They work 100% of the time in every other platform. I also have to do weird things to get the safe viewport measurements to work in my PWA, again, only in mobile Safari.
I’ll tell you what, you try asking customers to go toggle a feature flag and tell me how that works out.
Safari is almost always the last browser to adopt a standard, often times years after it’s been standardized. And don’t tell me it’s because they take their time to get it right, because their rollout of Web Push was atrocious.
OK you’re speaking from a completely different point of view then. I was more curious about what I would be missing out on using Safari right now. Definitely not thinking about how a project I paid somebody to create is going to render.
You’re missing out on the things people can’t create because Safari is holding the industry back. Just because it’s not a user facing problem doesn’t mean you’re not affected as a user.
I hear you and understand where you’re coming from now. It just doesn’t help me visualize anything.
Sounds like a skill issue xD
Skill doesn’t matter at all if Safari doesn’t support the API.
For example, my D&D group uses Virtual Table Top software to play. The software can’t run on Safari. (don’t ask me why, I’m just a user)
Interesting. What’s the software?
Foundry vtt