8,489 karma · joined April 26, 2010
Segmentation fault (core dumped)
https://www.cringely.com/2026/05/27/where-the-heck-have-i-be...
Consider your cloud costs.
Be careful of PDF's with built in broken fields though, in which case I just add a text field on top if it's easier.
If you understand how generative models and agentic coding works, it's not a surprise. But for some reason it's still mind boggling to think that you can take very old stuff and build impressive programs.
Please just stop with this AI slop. Flagged
Also, what do you really think the odds are that sigabrt.dev will still exist in 2 years from now? Or 5?
That's a user error, you simply had "This Mac" selected (preselected) instead of narrowing scope to be Applications.
In fact, I think Google's been saying this for 6-7 years already.
The abstraction is huge advantage, especially when targeting different devices and screen sizes. We (and that includes Apple) have been learning the value of those kinds of abstraction boundaries for years, well before React.
It's also important to note that SwiftUI and UIKit are composable, so if some small part of your app needs low-level, finer grained control, then go ahead and use UIKit/Core Animation/Metal and SwiftUI for the rest.
At his point I think that one has to assume that almost every author is using AI to some extent. And even if they don't, their editors will apply changes, no doubt using ChatGPT and other tools.
It's a crisis in literature. How do we fix this?