Excited to share a sneak peek of my latest project, TuneTally! 🎶 It's an app designed to help you explore music charts across various streaming platforms, with the added flexibility of selecting different countries. Would love to hear your thoughts – is this something you'd be interested in? 😮 #buildinpublic#swift
@SENTINELITE@MuseumShuffle Thank you very much. ❤️ I'm also happy to add you to the beta if you'd like to give it a shot, no pressure if not of course!
This update includes a lot of small improvements, namely a keyboard shortcut for searching packages (available in macOS 14+) and some prep work for the new way of validating licenses.
It now includes much more information about a service! You can also searh for a specific service using the search field, much like in the main Cork window.
In the release after the next one, the services might be read-only. I'm not sure if I'll have enough time to implement the turning on/off of services, but we'll see!
Experimental support for generic noncopyable types in the #swift standard library is now available in the nightly toolchain.
Here's a simple demonstration of adoption of this feature on the Swift Playdate example project. Switching the Sprite type from an enum+class box to a simpler non-copyable struct drops binary size from 7k to 6k on the SwiftBreak game.
And it is a serious topic to us (the company). Do you know how to do #Apple SignIn with one Apple ID on different apps (iOS, macOS) to get the same Realm user?
There are times #swift unicode behaviour just gets annoying. The following will end up failing:
let text = “Some\n\nText”
let regex1 = /[\r\n]/
let regex2 = /(\r|\n)/
let slice1 = text.replacing(regex1, with: " ")
let slice2 = text.replacing(regex2, with: " ")
assert(slice1 == slice2)
After ~15 mins I remembered \r\n can be a single char. to get (roughly) the behaviour wanted and still using a set it needs \r and \n flipping. So [\n\r] or to cover the single char [\n\r\r\n]
@daveaknight I love that I have, and am old enough to have used before, an ASR33 teletype where CR and LF are very different characters and do something very tangible (and loud) with print head and paper feed.
@mattiem I'm using callbacks at the moment, but would love to ue async streams instead. The rest of my code is async/await, so it feels out of place :blobcatpopcornsweats:
I can't resolve known good packages from github. & searching has failed me.
I get 1 of these 2 errors. Unclear why it seems to alternate. API token has FULL access. SSH Key verified (by me and it). HTTP & SSH cloning configs both fail. Wifey can install the same package(s) just fine.
"realm-swift" is irrelevant. it's just a known good package & version to eliminate potential errors related to the package itself.
The separate XCode bug we encountered:
I've been doing this a while & have been forced to jump through the 6 hells of GPG signing many times over the years. Consequently, I have my ~/.gitconfig configured Git to auto-sign all of my commits, with my SSH (not GPG) key.
I like knowing that all my commits to my public repos can be verified & weren't some malicious BS. You can fake the name & email on a commit trivially.
However, if I make a new XCode project w/ git it does this. 🎉
🧵5/?
This isn't actually a problem for me because i never use IDEs to manage git.
So, XCode can't handle GPG signing configured git setups, their error messages are god-awful, and I think they're absolute 🍆's for bundling all their 💩 into their 💩 IDE.
You know who doesn't use XCode at Apple? Everyone‡ who isn't coding in Swift/Obj-C. I'm not kidding. NONE of my coworkers used it. Why? Because there are tons of great IDEs / Editors out there that aren't XCode.
I've got a mac app that I've been avoiding touching because the last time I tried to sign it was an effing nightmare. But that was years ago.
Today I opened it up to see just how many compliation errors it had, and how much / if they've improved signing for distribution outside of the app store.
I was greeted with this lovely dialog which makes me want to touch it even less.
@masukomi With that amount of code, it would be easier to fix the errors manually than trying to install and run Xcode 10.1 on a Mac running a recent version of macOS.
@swiftdevjournal thanks for the confirmation. That was the conclusion I came to too. I know very little about swift, but a lot about code, and most importantly I have a smart wifey, who can help me.
@kharrison I would expect that calling sleep within a function marked to run on the main actor (main thread) will block, regardless of the function being marked async. I suppose adding nonisolated removes the MainActor requirement and then runs within the view’s task context.
