(no title)
fifafu | 2 years ago
With the right engine basically any kind of app could be created as a webapp / pwa
So in the US it doesn’t matter because users are still stuck with Safari there
fifafu | 2 years ago
With the right engine basically any kind of app could be created as a webapp / pwa
So in the US it doesn’t matter because users are still stuck with Safari there
troupo|2 years ago
Do you know that the only "alternative egnine" that implements hardware APIs is Chrome? Because it's a Chrome-only non-standard that Firefox opposes, too?
p_l|2 years ago
I wish Firefox had WebBluetooth or another API that could do that.
But then Mozilla instead of helping set codec standards that everyone could use preferredyto show you could run codec in JS and opened a way for EME
fifafu|2 years ago
I don’t think Apple can tell alternative browser engines what features it will allow and which not. Or is there something in the EU regulation that says browser engines must follow a standard?
szasamasa|2 years ago
only safari and firefox did not implement it according to: https://caniuse.com/?search=web%20bluetooth
which might be great because you have the choice...
and you can use open source chromium or brave (like the jvm to run cross platform java) to run web apps seemlessly that need web bluetooth or such but use safari or firefox for personal use if you find them more secure
I mean using chromium engine as the running environment where chromium only ever runs special trusted web domains and never goes to other "malicious" web domains that may fuck up iOS as Apple claims would be still a secure choice
like you will not download spyware from Apple Store because you are an adult not because Apple can protect you there