News for hackers. Stuff that matters.
Re:Improving Firefox Responsiveness on macOS by saagarjha on Monday October 10, 2022 @07:42PM (#33157691)
With all due respect, you’re a small indie developer, and the situation is different when you make a browser used by millions of people. Apple does do whatever it wants, but sometimes it (wisely) realizes that what it wants is people to not be upset that people’s favorite app is broken in the next release of macOS, so occasionally steps are taken to ensure that doesn’t happen. This ranges from committing to SPI for longer than it is necessary for Apple’s own use, to putting in bundle ID or linked-on-or-after checks, or in rare cases reaching out to developers directly.

The target for this comment is developers like you, but those who are less familiar with the platform than you are but of similar import. Those are the ones who will read this and say “wow Firefox says this is how to make my app fast so I should do it!!1!” and what is going to happen is either they’re going to use it wrong, because they aren’t really experts on how locking works, or they’ll copy the code of of Firefox and their app will break in a future OS release while Mozilla will update their code in July.

Re:Improving Firefox Responsiveness on macOS by lapcat on Monday October 10, 2022 @08:00PM (#33157830)
> Those are the ones who will read this and say “wow Firefox says this is how to make my app fast so I should do it!!1!” and what is going to happen is either they’re going to use it wrong, because they aren’t really experts on how locking works, or they’ll copy the code of of Firefox

You can't save people from themselves, but in any case this seems to overlook what I said at the end: "the majority of applications weren't even using lower level primitives like OSSpinLock in the first place, so replacing it was not a concern."

I wouldn't worry about native Mac developers, who I suspect are mostly a dying breed of grizzled old veterans nowadays. To illustrate, I noticed recently that the last post on https://www.reddit.com/r/macprogramming/ was over 2 years ago, April 2020.

Re:Improving Firefox Responsiveness on macOS by ccakes on Monday October 10, 2022 @10:51PM (#33158935)
Counter argument - https://www.reddit.com/r/swift/ has posts within the last few hours.

Granted Swift is technically a cross platform language but it feels safe to assume that the vast majority of users are developing for macOS and iOS.

Re:Improving Firefox Responsiveness on macOS by lapcat on Monday October 10, 2022 @11:39PM (#33159272)
> the vast majority of users are developing for macOS and iOS.

The vast majority of Swift users are developing for iOS.

The article is about macOS and private API. Thus it's only relevant to a small subset of developers who write native Mac software distributed outside the App Store.

Re:Improving Firefox Responsiveness on macOS by girvo on Tuesday October 11, 2022 @01:52AM (#33159930)
The vast, vast majority of the posts on there are for iOS development. macOS barely gets mentioned.
Re:Improving Firefox Responsiveness on macOS by saagarjha on Wednesday October 12, 2022 @04:26AM (#33174327)
I just got a message from a contributor to a popular macOS project I work on about this blog post and how it can help improve our performance, so I think you're mistaken.
Re:Improving Firefox Responsiveness on macOS by lapcat on Wednesday October 12, 2022 @07:28AM (#33175403)
> so I think you're mistaken.

What exactly do you think I'm mistaken about? The conclusion of your sentence doesn't follow logically from the first clause.

The readers of your comment here know nothing about this macOS project or the contributor who sent you a message. In any case, there's a vast gulf between someone sending you a message and someone actually writing and releasing bad code.