91–100 of 167 posts
Earlier quoted context omitted.
>that Apple's browser engine ban on iOS in anti-competitive and distort the browser market Isn't this a good thing? Without this distortion, what is preventing the web from becoming fully dependent on the Chrome engine?
Competition from Apple? Why would people use Chrome if Safari is as good or better?
Earlier quoted context omitted.
> Inability to have non WKWebView type browsers. Safari can do the one it wants, which is Apples choice. This is primarily for privacy and security reasons. One wouldn't want a funny casino app, or the likes of Google or Facebook to hijack people's web access. Another aspect is the user experience - a piece of web content will render exactly the same way anywhere on the system. There is no need for people to be conce…
I work for a product agency, and the ability to rely on Safari has unlocked many possibilities for us. It's significantly easier to create a unique and beautiful experience (web or native) for iOS than it is for Android. This is further facilitated by the consistency and performance of the iPhone platform itself.
Earlier quoted context omitted.
What's wrong is that you're stuck with the same shitty browser engine. If you encounter a problem with WebKit, you're screwed. Think it through.
Quoted post unavailable.
Okay, let me give you an example. One of many I have. I run a website. I have many gigabytes of audio files. I'd like to 1) not have to store multiple versions of the same files, and 2) I'd like to encode them using the most efficient codec available. This means I'd like to use Opus. Every browser supports it since *6 years* ago.... except Safari.
Okay, they technically support it, but only in their own special snowflake container - `.caf`. So what I did recently - I wrote an on-the-fly demuxer which remuxes the standard Ogg container in which Opus audio comes in into `.caf` files on the fly. Yay, it works! Audio now plays on Safari! A single guy did something in one evening that a trillion dollar corporation can't do in 6 years. (Okay, fine, doing it on their side would probably take more effort and probably take, like, a week. But still.)
....except a new iOS update comes, and.... oops, users report that the audio stopped working?! Apple broke it, because of course they did; they only pretend to support Opus, otherwise they'd just properly support it like everyone else.
But I'm stubborn. I tried to find a workaround and... I did. The trick was to decode the `.caf` file through `AudioContext::decodeAudioData`, remux it to `.wav` in JavaScript and then play it. Yay! Audio now works in Safari again!
....except I'm already looking forward when they break something else in the next update.
There are many other issues I have or had with Safari, and... I just hate it with a burning passion. I never have issues with Firefox nor Chrome, but I always have to add weird workarounds for Safari bugs. I know the "intended" way of alleviating this pain is to just give in and let Apple extort 30% of my income and write a native app, but that's just not an option for me. I don't have the resources to write a native app nor the will to be subject to Apple's bullying.
Earlier quoted context omitted.
The rendering engine is less important than the JS apis. Safari is missing half of them and some of them are flat out broken.
Safari is not missing anything of value: it's mainly access to USB, Bluetooth and such which have no place in a browser. And Firefox doesn't support many of them either. It's just Google trying to get more data about you.
Earlier quoted context omitted.
What's wrong is that you're stuck with the same shitty browser engine. If you encounter a problem with WebKit, you're screwed. Think it through.
Quoted post unavailable.
Earlier quoted context omitted.
The rendering engine is less important than the JS apis. Safari is missing half of them and some of them are flat out broken.
Safari is not missing anything of value: it's mainly access to USB, Bluetooth and such which have no place in a browser. And Firefox doesn't support many of them either. It's just Google trying to get more data about you.
Earlier quoted context omitted.
Competition from Apple? Why would people use Chrome if Safari is as good or better?
"This website works only in Chrome" or "Please download chrome to continue" might become common occurrence on Safari iOS forcing people to stick to Chrome on iOS
The only reason devs would show a "download chrome to use this" prompt would be if Safari were behind in support for the necessary features or if Safari's bugs are too much of a hassle to support (i.e. lack of push notifications, lack of web FS/BT/serial if the web app needs that, or a lack of provisioned browser storage that the mega.nz website relies on).
What I expect to happen, and what the recent expanse of the webkit team suggests is already happening, is that Safari will get better once it gets competitive pressure from Chrome and other browsers.
It's interesting to hear Apple always talk about the level playing field they've tried to create. From within the company i think they really believe they've got a level playing field. But then Apple has apps that can do much more than everyone else has access to, in ways that have nothing to do with security or privacy. - Apps access to NFC (e.g Apple Pay vs you being able to make your own nfc card) - Inability to h…
Access to NFC is a huge one. This has a ton of use-cases in for instance IoT and smart home, and Apple limiting access prevents a lot of innovation in that space which might compete with their offering. Another example is Apple's privileged access to your wifi credentials. Basically this means if you want to share wifi access via your app, as you might want to do in setting up an IoT device, this is only possible if…
Earlier quoted context omitted.
Safari is not missing anything of value: it's mainly access to USB, Bluetooth and such which have no place in a browser. And Firefox doesn't support many of them either. It's just Google trying to get more data about you.
Have you tried to use indexdb on Safari?