Want to learn how to develop an image classification app with swift and CoreML? Then wait no longer:
https://thinkpractice.nl/post/zooscan/
This is the first post in a series that will develop an iOS app called ZooScan: the ultimate companion for your zoo visits!
@nicd You can also write it in #SwiftLang 
https://github.com/Lighter-swift/Lighter
That experimental #SwiftLang macro pre-build SwiftSyntax feature is macOS only, correct? So it actually won't help w/ build times on other platforms?
Tickets for server side #swift conf in london are up for sale now!
Last year was really really good, can't wait to see what use-cases and experience reports we'll see this time :-) #swiftlang
Using a custom random number generator can significantly improve performance over Swift's default random generator. For example, wyrand is 50x faster than Double.random in Swift when filling an array of 100,000,000 elements. #SwiftLang #macOS https://gavinw.me/swift-macos/swift/random-array.html
Experimental pre-built Swift-Syntax in SwiftPM! 
```
swift build --enable-experimental-prebuilts
```
https://forums.swift.org/t/preview-swift-syntax-prebuilts-for-macros
Here’s how Send to Mac works in the new Proxygen app. You pair up the Mac app with your iOS device and it’s ready for traffic mirroring whenever you need it. It works even when the iOS device is locked!
Oh, and it already supports more series than just two.
Plotty reads from stdin, i.e. you simply run this as follows to process data on the clipboard for instance:
pbpaste | plotty
I still need to add proper arguments like -o <output filename> and width and height parameters for the canvas, labels etc but for quick visualisation of benchmark data it's already useful.
It took very little time put together a little tool which I called "Plotty" that does that and thanks to Swift Charts, I think the result looks much nicer than gnuplot.
#SwiftLang (3/3)
Finally, my #Swiftlang #ATProto API library, ATProtoKit, has now been updated to version 0.26.0.
SessionConfiguration and ATProtocolConfiguration have been revamped for better session management and token handling, with actors for UserSession and keychain management.
#atdev
GitHub - MasterJ93/ATProtoKit ...
It is *very* tempting (and easy to fall back to) but my recommendation for #SwiftLang concurrency is the same I have for #SwiftUI. Do NOT try to map your existing knowledge to the new system. An actor is not a GCD serial queue, just as a SwiftUI View is not the same as a UIView.
You essentially have to learn both from scratch, prior knowledge is more of a distraction leading to wrong paths of thinking about them.
Those things solve similar problems, but are very different things.
New Proxygen version is now available. Almost every part of the app has been updated. Perhaps the biggest thing is that there is now a direct download at https://freshbits.fi/apps/proxygen/.
SK8 has some clever ideas, like VirtualType (basically retroactive protocol conformance on classes you don’t own like in #SwiftLang), but it also does some things AppleScript luckily rolled back.
You create new handlers using a dialog panel, like you'd name a new file. That's slow. Also, a handler in SK8 looks like:
on mouseDown of me (a Board)
drag me with live
end mouseDown
So they threw out the English syntax right from the start (vs. AppleScript, where they just don't enforce it)
3/6
Almost missed it - today is @SwiftPackageIndex‘s 5th “first commit date”! To celebrate, we finished adding full support for #SwiftLang 6.1 and have started processing thousands of Swift 6.1 builds 
Thanks to @daveverwer for the great collaboration and to all our supporters and sponsors. It wouldn’t be possible without you! 
Ever wanted to form a key path to a method or initializer? The authors of SE-0479 did too! Their proposal is in review: https://forums.swift.org/t/se-0479-method-and-initializer-key-paths/79457 #SwiftLang
Reminder that SwiftPM package manifests are Swift code, so you can write loops etc. in them. I use this in some of my packages to enable the same upcoming language features for all targets. Example: https://gist.github.com/ole/c0f4de915a483edb5e6df5f1ad677fb5
This isn’t particularly useful for complex projects where you might want to migrate to Swift 6 mode module-by-module, but for small and simple packages it’s usually easy to stay on the cutting edge of Swift. #SwiftLang
![Swift code:
let upcomingFeaturesPostSwift6: [SwiftSetting] = [
.enableUpcomingFeature("ExistentialAny"),
.enableUpcomingFeature("InternalImportsByDefault"),
.enableUpcomingFeature("MemberImportVisibility"),
]
for target in package.targets {
guard target.type != .binary else {
continue
}
var swiftSettings = target.swiftSettings ?? []
swiftSettings.append(contentsOf: upcomingFeaturesPostSwift6)
target.swiftSettings = swiftSettings
}](https://assets.chaos.social/media_attachments/files/114/381/264/989/999/231/original/5cae5ca2cb1ee4e2.png "Swift code:
let upcomingFeaturesPostSwift6: [SwiftSetting] = [
.enableUpcomingFeature(\"ExistentialAny\"),
.enableUpcomingFeature(\"InternalImportsByDefault\"),
.enableUpcomingFeature(\"MemberImportVisibility\"),
]
for target in package.targets {
guard target.type != .binary else {
continue
}
var swiftSettings = target.swiftSettings ?? []
swiftSettings.append(contentsOf: upcomingFeaturesPostSwift6)
target.swiftSettings = swiftSettings
}")
Starting a blog about Swift can be beneficial for learning, sharing knowledge, and networking with other... https://wesleydegroot.nl/blog/Start-your-own-blog #blog #programming #iosdev #swiftlang
Jumped back on the #100daysOfSwiftUI train 
and completed day 36, a simple expenses app.
Getting back to it after a few months away took some considerable mental effort. Couldn't remember a lot of the specifics of what went before, but there was plenty of residual memory of concepts intact in my brain 
which made it easier than I expected!
Glad I’d been taking copious notes throughout, and thankful the site's search is super useful! https://www.hackingwithswift.com/100/swiftui/36
