SwiftUI connoisseur.
I don't typically rag on specific stuff, but today the quality of Apple's documentation is absolutely *killing* me. How did we ever get to the point where we get docs published like this? No examples? No explanation? No suggestions for alternatives? No information on customizations? Just a ridiculous regurgitation of useless information that I already have.
It's so demoralizing to realize just how much of the docs are like this.
https://developer.apple.com/documentation/swiftui/blendmode/darken
One of the things I fantasize about is a startup that basically attempts to sherlock Apple's own WWDR and DevPubs orgs and offers it to developers free of charge. Income would be from consulting + specialized sample code + priority access etc.
I think I could make an absolute killing doing it.
@schwa insult to injury is that even if you’re motivated enough to build your own, full-fledged replacement - the means of deep integration are gated by internal or private SwiftUI APIs. Almost all the best OSS SwiftUI component libraries that I’ve seen end up resorting to some private API and/or Reflection (which has a massive performance cost).
Like fucking fix it, or let others fix it for you.
@b3ll @jamesdempsey I’ll be there as well! Looking forward to meeting so many of you wonderful folks in-person finally!
@tonyarnold I’ve posted in detail on Swift forums about this, and just so that there’s no confusion - I think Swift macros are wonderful and I’m excited about the way the feature is being implemented.
To advertise it as production ready and usable while tied to a source dependency on swift-syntax is what utterly baffles me and other members of the community.
@tonyarnold what, in your opinion, is the fastest solution to the burning issue of swift-syntax build times? The official response to it has been to acknowledge the issue but no timeline has been provided.
I am personally shocked at the pathetic way in which Swift macros have been rolled out, this is a beta feature at best being paraded around as generally available. The build time regressions for adopters alone are untenable by any industry standard. I am not alone in this opinion.
🍕 Speaker Session Info
"Is Your App Secure? Revelations a Jedi Wouldn’t Tell You" with @kabiroberai
When: May 7th at 2:00pm
The topic of app security often focus on the blue team perspective centered around defense. This talk takes a different approach — the offense-oriented red team approach. ⚔️
@NeoNacho @tonyarnold 100% agree with this.
For whatever reason, progress on shipping SwiftSyntax as an XCFramework has not been made yet, even in an opt-in-only fashion despite being demonstrated as a viable option by multiple members of the Swift community. There is no concrete timeline on when the acceptable way of shipping binaries is going to be shipped by Apple (AFAIK).
Anything that shaves 3-12 minutes from my release build times is worth investigating interim.
@bryce you're an absolute legend.
@finestructure @adityadaniel please dupe FB13561625.
@qzervaas @willrbishop I don't think that's a valid comparison. This is clearly a bug in the way Apple chooses linker defaults.
@bens UICollectionViewLayout is also pretty weird.
I've decided to take the old #Macintosh HIGs & merge them into one large collection of topics while modernizing them in the process.
The original #HIG would give actual examples w/ usable metrics & mention possible exceptions to the rule. The incredible level of detail gave developers the guidance to create delightful UI users have come to expect from their #Mac.
Here is my first topic: Layout Guidelines
@Migueldeicaza hey hey!
