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.
When I left android, I was jailbreaking on iOS, so generally had all of those features, but funny enough probably about right when you left extensions, VPN ad blockers, etc. came out. Officially and polished.
Debugging (without a MacBook). Webgl 2. WebXR. Local storage not being completely gimped. I'm glad I don't work in that industry anymore, Safari was the bane of my existence...
Good web standards are a threat to the app store (particularly anything to do with ARKit) - not like 3rd party browsers are likely to change that much with the majority of users sticking to defaults, but it might apply some pressure
Which ones are you needing? For Adblock I block using VPN, similar to setting up a pihole. I’ve found replacements for most of what I do use elsewhere. Some working even better then the desktop counterparts.
I have a pihole at home so it’s really when I am out and about but I’ll check out VPN offerings. The last time I used a vpn it really hit my battery hard but maybe it’s better now. Other than that it’s just the plugins to get rid of the cookie screens and additional YouTube ads.
True, but if we're have to have a monopoly of browsers, I'd prefer that the monopoly browsers were actually based on a good engine, rather than one based on an engine that falls over if you look at it.
Isn't this what everyone wanted though? The freedom to choose browsers? Or are we going to start mandating Gecko because that's what everyone here believes to be the most ethical?
From an idealistical point of view, sure freedom of choice is the way to go.
What makes me nervous is that Safari has been the only big player left besides chrome in regard to usage share on mobile. So while from an idealistical point of view the ban of other engines was certainly a bad thing, it still helped to prevent google from extending its monopoly.
The antitrust office is actually about the oldest part of the EU, with roots back in the ECSC: They saw the need to get rid of internal collusion to actually entwine the national coal and steel industries. Think of it as a bigger bully saying "We're the cartel bosses around here".
I'm all for this change, but hopefully it means Mozilla will put some more energy into Gecko to make it competitive with WebKit in speed and multimedia capability (P3 colors, HDR images, JPEG-XL, etc)
Same. Overall, I'm happy with my iPhone, but not having an actual browser with an actual ad blocker (uBlock Origins) is really painful. I've had to live with ProtonVPN's ad blocking, but that only prevents sites from loading, it doesn't hide the actual ad links...
Maybe, but Safari has a dogshit UI and I much prefer Firefox over it. I despise the fact that they don't let other browsers use their extensions, though (even though they're forced to reskin Safari). I'd install AdGuard on Firefox if I could.
I use 1Blocker for which I bought the lifetime license on my iOS Safari, as well as adGuard DNS blocking running on my OpnSense at home (WireGuard automatically connects my phone to my home network via VPN as soon as I leave my WiFi)
Ok, apart from human rights, workers rights, rebalancing funds to poorer regions, free trade, free movement, a voice at the table, straight bananas, peace in Europe, and endless examples of consumer rights, what has the EU done for us?!
What about the straightening of cucumbers? And regulating the amount of cinnamon in baked goods? And the GDPR? And trying to take away the red sprinkles on my liquorice pipes?
The limit is not on cinnamon but coumarin. Which means that if you want to put a lot of cinnamon in stuff you have to use the good stuff (Ceylon), not the cheap knockoff (Cassia), where a single teaspoon of powder can exceed the maximum recommended daily dose of coumarin (for flyweights or just generally small people). If you're in the supermarket and it doesn't say which type of cinnamon it is, it's bound to be Cassia. When buying straight bark (not powder): Cassia will be thick, rolled pieces, while Ceylon is thin pieces rolled up into each other.
In practice it was mostly a seasonal issue, e.g. Zimtsterne contain ludicrous amounts of cinnamon and you try telling a kid it can only have one.
And while I'm at it, the cucumber saga: Like with many such things it was the industry who asked for a EU regulation as previously there were differing national standards and they couldn't readily agree on a uniform one. Long story short if growers grow cucumbers straight (not hard) and to a certain size (also not hard), then a certain amount will fit into a standard box, which will have an approximately uniform weight, and a certain amount of those boxes fit onto a standard euro pallet of which a certain amount fit onto a standard lorry bed. Thus, "I'd like to buy a lorry load of cucumbers" is something that makes sense, supermarkets know how many cucumbers they're going to get and they can sell them by piece, not by weight, and everything works out.
Tech sites have said that Mozilla probably has their native version already done so it's ready day 1.
But these new rules by apple might put a damper on them actually offering it. Mozilla is a non profit, and apple is going to require a $0.50 tax on every app "for each first annual install per year over a 1 million threshold".
I just don't see how how Mozilla could carry that cost considering they are at over 100 million installs on Android alone.