I recommend not clicking this:
https://neal.fun/stimulation-clicker/
=> More informations about this toot | View the thread
@gsuberland You’ve done some audio stuff, right?
What do you think about a PoE speaker, specifically for the purpose of providing ambient sound in a themed environment (like a Halloween haunt or theme park). PoE is like 12 W, right? That should be enough to power a simple bookshelf speaker at low-to-medium volume, no?
=> More informations about this toot | View the thread
Did something change in #SwiftUI under #Xcode 16 such that .toolbar {}
no longer compiles? Because it doesn't. It complains about the trailing closure not being of type Visibility
. This code was compiling just fine in the betas.
=> More informations about this toot | View the thread
Turns out, if you use a NavigationLink with label:, all hell breaks loose. #macOS #Xcode #SwiftUI
=> More informations about this toot | View the thread
Why is SwiftUI just so awful all the time?
I've built a simple example app showing the problem:
https://github.com/JetForMe/TestMultiSelect
[#]macOS #Xcode #SwiftUI
=> More informations about this toot | View the thread
Toggle buttons do more harm than good.
=> More informations about this toot | View the thread
DJI wants people to "take a dronie." Not sure how I feel about that, but holy cow this is incredible. A $200, completely autonomous selfie drone.
https://store.dji.com/product/dji-neo
=> More informations about this toot | View the thread
To my #macOS and #iOS devs, is a top-end Mac Studio so much more performant at #Xcode tasks than my current top-end M1 MacBook Pro, that it would be worth the hassle of having two different machines (I love taking my MBP with me)?
Related question: If I clone projects to iCloud drive, do they perform locally as fast as local storage? From what I understand, they do, since it’s all cached locally and synced separately. That might make it painless enough to be able to seamlessly work on Xcode projects.
My motivation is to wait less on Xcode. Apple doesn't seem to be in any hurry to fix the myriad performance issues in Xcode, but all the demos sure show it being snappy (even when people like @twostraws show demos). I wonder if that’s because they’re using a Mac Studio (or Pro?), rather than a laptop.
Is anyone successfully working in this way?
=> More informations about this toot | View the thread
=> More informations about this toot | View the thread
It’s so stupid that *Xcode can't have a project and a project dependency open at the same time. Worse, it doesn’t tell you that’s why it makes things look broken.
=> More informations about this toot | View the thread
I finally mounted my PC to the wall. I really need to put power and other connections in the wall behind it, but for now this will do. I’ve got white cables ordered and will tidy them up next week.
I don’t really use a PC much, but I’m working on some reinforcement learning stuff and this has an RTX3090 in it.
=> View attached media | View attached media
=> More informations about this toot | View the thread
My Lyft driver has a local radio station on playing Every Breath You Take. The screen says the genre is “Adult Radio”.
=> More informations about this toot | View the thread
@mattiem High-level advice question for you, if you have some time (if not, that's okay, just posing the question helps me think it through): I'm working on an app that uploads assets. You drop one or more images (or videos, or whatever) on it, it generates zero or more derived assets (think smaller versions), and uploads the original and derived files to a server.
All of this work should take place in the background. I would like for each operation to contribute to progress feedback to the user, both for each individual asset, and all operations as a whole. Each asset and the whole set should be cancelable.
How would you structure the concurrency for this? A top-level Task
for each asset that kicks off a TaskGroup for the generation and upload of each derived asset? An Actor that holds processing state for each derived asset? I find myself falling into Dispatch ways of thinking.
One of the challenges is that I’m using SwiftData, which can create multiple instances of an entity, making it harder for an entity to hold onto a reference to the tasks related to it (does that make sense?). All I can think of is some kind of keyed collection of “progress" objects, maybe keyed off the entity ID.
=> More informations about this toot | View the thread
I did not catch this 😞
=> More informations about this toot | View the thread
=> This profile with reblog | Go to JetForMe@geekstodon.com account This content has been proxied by September (3851b).Proxy Information
text/gemini