2026-04-02 14:57 UTC
Replies (2)
-
@NfNitLoop@mastodon.social 2026-04-02 17:39
@adactio I have not read the article yet, and am replying partly to bookmark this for myself to read when I have more time later. I do agree that Apple sometimes supporting their own standards instead of common/open standards is frustrating. (ex: requiring Apple audio containers for some codecs) BUT, I'm also wary of "The Web" requiring supporting *every* web standard and every feature that Google's Chrome supports. Web sites *should work* on older/smaller browsers, or for example, without JS!
-
@OneSadCookie@mastodon.gamedev.place 2026-04-02 20:26
@adactio @baldur as an iOS developer, this resonates for native code too. Between a third party solution where I can read the code, fix the code, and freeze the code, or a first party solution that Apple deliberately breaks every 12 months, I know where my trust lies.