mtomweb

9 ms·

91.
by mtomweb 4y ago
iOS does not allow for any meaningful choice, it’s all basically Safari. Says who? Mozilla, Google, Microsoft, EFF, the uk regulator, the Japanese regulator, the EU and most importantly the group of people who actually build web software on
92.
by mtomweb 4y ago
Again. People who ACTUALLY build apps in Safari are the ones that run into these issues. The only people that attempt to defend it are the ones who don't even build apps for it.
93.
by mtomweb 4y ago
Would you point me to Apple's alternative implementation for access bluetooth / nfc? That's right it doesn't exist. Instead they offer for you to install a native app which once granted bluetooth access can continuousl
94.
by mtomweb 4y ago
Exactly: Install Prompts - 7 Years. Fullscreen API - 11 Years. Push API - 7 Years. Badging - 5 years. Screen Orientation Lock - 11 years. Bluetooth - 5 years.
95.
by mtomweb 4y ago
You've got be joking right? ok so lets go through some stats: 1. Safari, performs worst on wpt.fyi by a VERY wide margin 2. In State of CSS last year had the most number of complaints in relation to bugs. 360 related to Safari, compa
96.
by mtomweb 4y ago
No. Safari is miles behind. https://wpt.fyi/results/?label=experimental&label=master&ali... Interop2022 is probably what your referring too but that’s just a small (but still important) functionality that the
97.
by mtomweb 4y ago
Minimum cost. That’s for a browser engine though. You can do a soft fork for far less
98.
by mtomweb 4y ago
Oh that second one is a nightmare. Our solution for it was to copy the element and create a new one that was absolutely positioned for the draggable element. The issue is syncing elements can be quite tricky.
99.
by mtomweb 4y ago
https://github.com/web-platform-tests/interop-2022/issues/84 << this issue we’ve had for at least 7 years. It’s never worked and to solve all the edge cases the workarounds are insane.
100.
by mtomweb 4y ago
I have not talked to a single team developing mobile apps for Safari that hasn’t run into significant problems. If you’re just building a standard body scroll website with a simple ui/ux you’ll likely be ok. As soon as you start doing
101.
by mtomweb 4y ago
Why can’t they bring their JITs? They’ve got better security records than Safari does.
102.
by mtomweb 4y ago
How does that explain the enormous number of major bugs?
103.
by mtomweb 4y ago
Mozilla’s has publicly stated in document to regulators that Apple’s browser engine ban delayed their entrance by 7 years and significantly impairs their ability to differentiate their browser. It’s not a stretch to tie that to the loss of
104.
by mtomweb 4y ago
How’s it fake grassroots? It literally got started by a bunch of no name developers
105.
by mtomweb 4y ago
Did you read the article?
106.
by mtomweb 4y ago
Regulation.
107.
by mtomweb 4y ago
In a lot of ways it's worse, Microsoft never banned the competition. It's utterly outrageous that Apple has been able to get away with such clear anti-competitive behaviour for this long. There's only one reason Web Apps are
108.
by mtomweb 4y ago
We were considering asking for this, but we’re just unsure how important it was and whether it would place an undue burden on manufacturers for more simple devices. Mobile devices are an obvious target for competition because they are just
109.
by mtomweb 4y ago
This article gives a much better summary. https://www.macrumors.com/2022/06/10/uk-to-target-apple-gami... It’s not “may face investigation”, it’s the start of the process to force Apple to support third party
110.
by mtomweb 4y ago
is that still a thing? I'm sure i've stored more than 50mb in idb before...
111.
by mtomweb 4y ago
>iOS experience would be if most developers used an off-the-shelf shoddy HTML rendering engine That's exactly what we have now. Developers are forced by anti-competitive rules to use by far the most buggy browser available. I'
112.
by mtomweb 4y ago
To mount a believable defense against third-party browser engines, Apple would need to demonstrate that their browser is more secure than rival browsers. In order to persuasively argue a need to ban all rivals, Apple would need to prove tha
113.
by mtomweb 4y ago
What specifics are you looking for? In Web Development circles the issues are fairly well known. For specifics: https://open-web-advocacy.org/walled-gardens-report/
114.
by mtomweb 4y ago
OSs need to restrict In-App Browsers to first party content only unless it is the users default browser
115.
by mtomweb 4y ago
Web Bluetooth is significantly safer than native bluetooth + the safest car is the one that doesn't start is not a good direction for the web.
116.
by mtomweb 4y ago
Mozilla seems to have come around with WebMIDI, so thats a good step in the right direction. The functionality is not limited to device APIs, it covers every aspect of the browser. See: https://open-web-advocacy.org/walled
117.
by mtomweb 4y ago
I think it's one of those things, that if you're not using Safari to develop Web Apps it's very hard to see what the problems are from the outside. If you get some time we've written a lot of detail about it here: htt
118.
by mtomweb 4y ago
The main advantage of the web is interoperability, if you don’t have that and the game engines developers just go for native. Once the core gaming APIs are supported across both iOS and Android (WebGPU, SIMD, WASM threads, fast storage, ins
119.
by mtomweb 4y ago
I understand the feeling, we’d stopped bothering to lodge tickets until this year. If you find ones that haven’t got attention and they’re still important, tweet at webkit or Jen. They’ve been really good with bugs recently and they are g
120.
by mtomweb 4y ago
It’s an awful business model. It’s one thing to have Safari hobbled because of high quality business apps and games, another for loot boxes, gems and countdown timers to exploit whales.

More ›