| Quiche Browser | @quichebrowser |
| Quiche Reader | @quichereader |
If you’re reading this on iOS, it’s really interesting to me that clicking this link will slide open an Apple One signup UI — right on top of your Mastodon client!
Now That’s OS Integration™
@atpfm @siracusa @marcoarment @caseyliss SwiftUI isn’t responsible for what you dislike about System Settings.
By default, SwiftUI uses the AppKit widgets. You have to *opt in* to different styles, which System Settings has done.
And you can quibble about those styles, for sure. But this is about the designers, not the technology.
Difference between the screenshots below:
.formStyle(.grouped)
.toggleStyle(.switch)
Otherwise it’s the same code in both cases.
The WWDC slack opened up today with all of the channel names redacted. The placeholder names are good, but I think I can offer my help here:
• no-objc-tions
• spoonful-of-syntactic-sugar
• mutably-we-roll-along
• the-callback-kid
• strings-attached
• push-pop-or-perish
• git-in-the-zone
• init-to-win-it
• guarding-the-galaxy
• one-if-by-clang-two-if-by-C
• entering-a-nullish-market
• multithreading-the-needle
• if-you-dont-succeed-try-try-a-catch
Web developers: when you say, “your browser does not support this site,” what you REALLY mean is that YOU don’t support the browser. Don’t turn it around on the user because you chose not to stick to well-supported standards, or worse, are doing user agent sniffing.
If you truly use some feature shipped by one browser and not everyone, at least say, “We use x standard feature, which is unsupported in this browser.” But even then, the web is all about progressive enhancement.
Max Kennerly
Michael Wyman
Cabel Sasser
Clarko
sam henri gold
Cassidy James 
Cody Kloepfer
kccqzy