HN user

TheNightman

36 karma
Posts0
Comments21
View on HN
No posts found.
Claude Sonnet 5 22 days ago

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.).

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).

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 (‘:

I remember when I got my second dose of gardasil I blacked out in the waiting room after and woke up on the ground with rugburn on my face. I later learned I had fallen over and had what appeared to be a seizure. I didn’t even know what it was I was being vaccinated for at the time, I was pretty young. I was a little peeved when I found out that, as a male, I didn’t even need the vaccine. Needless to say I’ve been skeptical of vaccines and the pharmaceutical industry as a whole ever since.

A viewmodifier can have its own @State, etc. I can’t think of anything that couldn’t be accomplished with an extension on View with a few tricks but ViewModifiers are easier & cleaner IMO. I usually have a ViewModifier along with an extension on view used to apply it

Never had a problem like this on Mac. When I shoot a video on my iPhone, it’s in the photo library on my Mac. Same with downloads, photos, passwords, safari tabs, clipboard and more. No transferring of files required at all, let alone through the Apple TV app?

Have these folks done any sort of actual audit on the Android code base to ensure they’ve removed _all_ of the “phoning home”? Not so much doubting their claims, more so just curious to see what they found. Is it possible google has baked in some tracking features deep in the OS, outside of gapps? Things you wouldn’t see with a mitm proxy? I’d be interested to know

This was my impression as well. I haven’t spent enough time with Rust to hold a hard stance on it but it definitely seems like it was not designed for “bare-metal” applications. I hadn’t heard of Zig before this but I’m definitely going to look into it now. Got any recommendations for a good intro to zig?