TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

These 299 macOS apps are so buggy, Apple had to fix them in AppKit (2018)

36 pointsby curling_gradover 2 years ago

7 comments

lapcatover 2 years ago
Author of the article: &quot;I admit that I was intentionally going for misleading clickbait headline.... I&#x27;m not a macOS developer (I&#x27;ve only done a bit of iOS)&quot; <a href="https:&#x2F;&#x2F;twitter.com&#x2F;zhuowei&#x2F;status&#x2F;998384740787896320" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;zhuowei&#x2F;status&#x2F;998384740787896320</a><p>What actually happens is this: Apple works in secret on the next version of macOS. Apple makes changes in the next version of macOS that break an app on the internal list of &quot;do not break&quot; apps. But Apple can&#x27;t tell the app developer about this, because the changes in the next version of macOS are secret. So Apple goes ahead and patches the apps to maintain compatibility. In fact, Apple is so secretive that it may <i>never</i> tell the app developer that their app has been patched by the system frameworks, much to the frustration of the app developers themselves.
评论 #34035923 未加载
bhaneyover 2 years ago
It seems less like these apps were &quot;buggy&quot; and more like Apple broke backwards compatibility and internally applied some workarounds to make the most popular apps continue working without intervention, while developers of less popular apps were forced to deal with the compatibility breakage themselves.
pmontraover 2 years ago
&gt; Apple’s using the compatibility system to patch other things&#x2F;change behaviour for specific system apps. Shouldn’t that be done via, say, method swizzling by the app itself, instead of in the framework?<p>I can see internal discussions like in any other company, along the lines of: we don&#x27;t have time or resources or budget to fix our app for the new version of the OS. The framework team does because they have to test and fix third party apps, they fix our app too. Then this becomes normal.
sircastorover 2 years ago
I’m surprised to see a couple of Panic’s and Omnigroup’s apps on the list. I’ve always looked at those two companies as the favored children of Apple Development. The kind of folks that stay up late to be the first to release updated apps for the new OS.<p>Granted, this list is a couple of years old…
dangover 2 years ago
Discussed at the time:<p><i>Apps for which macOS applies compatibillity fixes</i> - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=17116106" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=17116106</a> - May 2018 (125 comments)
leohover 2 years ago
So if you just change the bundle id of a development build, one is liable to introduce a bunch of bugs. Whew, that sounds confusing to debug.
laudecumover 2 years ago
I’m kinda confused.<p>1. Some apps are open source, why not just send a PR?<p>2. Most apps are actively developed, why not just send a report?<p>I’d understand this 20 years ago when updates weren’t frequent, or if software was rarely updated. But patching Firefox in your OS feels completely unnecessary.