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 /:
I have absolutely no doubt that an experienced SwiftUI macOS developer could easily produce better UI than Claude can today. The thing is, Claude produces better UI than a replacement-level macOS developer can, and, much more importantly --- this is really the core of my argument --- \infty better UI than a typical developer can produce, because most developers don't ever build native UI.
If I'm shipping a product where each development/release cycle costs my team $5MM, I am absolutely going to spring for the professional SwiftUI developer.
But most things normal developers build in their spare time don't even cost $50 per cycle. Unless they're UI learning projects or projects by UI experts, there is no "budget" for UI. At best, for real labor-of-love projects, you get a TUI where the developer spends 5 hours of their life that they will never get back creating a 70%-functional terminal version of the affordances the native UI toolkit provides out of the box.
That's all over now. However competitive Claude-generated SwiftUI user interfaces are with expert SwiftUI projects, they roflstomp the UI options available to most developers. I can't say enough what a smoking gun the flickering Signal app is here!
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”.
On Feb. 15, 2023, EGodly thanked Coristine's company for its assistance in a post on the Telegram messaging app.
"We extend our gratitude to our valued partners DiamondCDN for generously providing us with their amazing DDoS protection and caching systems, which allow us to securely host and safeguard our website," the message said.
This isn't about whether or not Coristine should go to jail for EGodly's criminal activities. This is about whether Coristine has the maturity and moral integrity to be accessing government systems.
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.
As per the US constitution, removing funding for federal agencies requires congressional approval. What DOGE is doing has not been approved by Congress. DOGE has removed funding for federal agencies, such as USAID. It follows from these three premises that DOGE is acting unconstitutionally.
Obviously, IANAL. I took it from reading various news articles. You can find more online quite easily.
as a hypothetical, if the prez defined 'proper security clearance' as opening up http (unencrypted) access and clicking OKAY on the website (or many with all this data), allowable to anybody on the internet to access said data.. would you be okay that it was happening?
my point is that "proper security clearance" is subjective, and as we are observing, (from what i read the other day) "clearance" is given to folks who would have never made passing the clearance checks in the very recent past (lol like a few weeks ago recent past).
is it all lawful? time will tell, and thats what EFF and others will try to decide - and good luck if any of that data is ever properly disposed of and not benefited from (aka insider knowledge).
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).
Swift Concurrency as a feature set includes async/await and async for, which solve a large part of Combine's same problem with better safety and less setup/teardown. These days Combine is still useful, specifically for multiple observers and several cases of adapting to older event publishing sources.
Because not all presidents have served for two full terms. Examining things while ignoring the time period over which they happened does not a meaningful analysis make.
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
Having it cache a bunch of crap to your disc isn't exactly "borking your shit". Just delete it. There's probably some settings flag you can export in your shell .rc to control that behavior, but its so not a problem it hasn't been worth my time to go look up how to do it.
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 /:
reply