TheNightman

nix-Darwin is great, but it doesn’t really make sense in combination with brew. You can manage brew packages in your nix-Darwin config, but I’ve found no need to as of yet

Same price for worse performance once you go above medium effort seems kind of silly to me. Especially since low and medium effort seem to perform so poorly compared to opus. I guess similar performance at xhigh will be nice to have for folks that never touch that sonnet usage limit.

I’m a SwiftUI developer at $DAY_JOB so maybe biased but while Claude can make things that look right it’s still not exactly perfect. Especially from designs. I used Claude design to mockup a monitoring app for my talos cluster and Claude code totally freestyled it. What should have been as simple as `List { Section(“title”) { … } }` got morphed into whacky DIY `VStack {}.background(.gray)` nonsense.

It looks off and it’s suboptimal performance-wise. It was, I’d say, 80% of a proper SwiftUI app (which is really fantastic given it was basically a one-shot).

Actually knowing SwiftUI meant it was trivial for me to just close out that remaining 20% by hand and have an actually *nice* cross platform (iOS, iPadOS, macOS) app.

I’m sure I could have prompted it to get it done right but without proper knowledge on the subject I wouldnt even know what was wrong and Claude doesn’t do so hot with “that just feels wrong”. Beyond that it was quicker to do it myself, but maybe I just need to prompt better /:

That’s why you should break out all of your code into SPM packages/targets. The workspace code only really needs to be the entry point, lifecycle and maybe target-based dependency injection (if you’re into that) or environment config since your SPM dependencies don’t know about your projects preprocessor macros (I.e. `#if DEV` `#if APP_STORE` etc.).

I feel like I’m taking crazy pills, did anyone read the article? He ran a CDN. Unless I missed something, there doesn’t appear to be any reason to believe he knew it was a “cybercrime ring”.

> If you are using M1, you will have to run cargo build --target x86_64-apple-ios instead of cargo apple build if you want to run in simulator.

Does this mean simulator will be run under Rosetta?

If you already have a domain and iCloud you can create an address on your domain very easily

Please pardon my ignorance but why is it unlawful for DOGE to be accessing this data? I was under the impression they had proper security clearance and were given lawful access by the president somehow.

Yeah I jumped into swift on Linux a while back having mostly used it on apple platforms and I couldn’t even tell anything was different. A few years ago I would’ve had to struggle with SwiftNIO but not nowadays. URLSession, Codable, etc. all there on Linux (not sure about Combine but Combine is stupid in the Swift 6 world IMO. Swift concurrency is better in almost every way).

Swift on Linux (except NixOS) is actually very good nowadays. There’s even a libadwaita library that feels a LOT like writing SwiftUI.

Feels like a lot of folks were turned off early on, found something else, and never bothered to try again (which is fair).

Why would you look at it “per year” when speaking in terms of “per president” other than to say “except trump”

Brew winds up hogging an inappropriate amount of disk space on every system I’ve ever installed it on. I switched to nix recently and haven’t had that problem yet.

That being said I haven’t investigated and it could be user error. But brew can absolutely bork your shit

If you think this is bad, try an Apple TV app! A lot of the platform APIs, like the one mentioned in the article, are still in objective C and really beginning to show their age. The worst is when you want to do something in SwiftUI but the platform APIs are UIKit (‘: