We're 10 years into Swift wrapping Objective-C API and still haven't covered nullability. I think the same is about to happen with the "Sendable" requirements and Apple frameworks.
how it started: UIKit api crashes because it get nil value and not Optional
I noticed my disk storage went drastically low and I started to check system, then I realized something ( #macos update???) enabled iCloud Photos synchronization to my Mac (that can take all the storage it get, and for that very reason I didn't enable it on my mac)
@finestructure Yes, the VS installation is still required. That is what provides the headers for ucrt/vcruntime. VS then doubles up as a means for installing the Windows SDK which is available standalone. The toolchain distribution includes everything else (compilers, linkers, debuggers, IDE tools, etc).
my big privacy related question is: why (seriously why) Apple keeps deleted photos on their servers indefinitely? for what really? and how that aligned with the privacy of the iPhone statements
bugs happens. that is not just a bug. that is a bug that surfaces the questionable design decisions.
@krzyzanowskim I suspect these are not on Apple’s server but in a temp folder or volume on the device, and the update scans that folder and reimports them. Restoring on a device that has been wiped throws a wrench into the works as the device encryption should make them unreadable on the wiped device. That implies not just a temporary folder on device, but a file system container that is not included in the device encryption.
@krzyzanowskim This is pure speculation and I am not an expert in this stuff.
(1/2)
USB flash drives, sd cards, solid state drives, etc distribute writes across alot of different blocks to increase the life time of the memory (aka wear leveling). Most flash memory devices are utter crap, however, at fully deleting data because of that. Formatting nor blasting out the flash countless times with boatloads of 0&1’s works if the internal memory controller isn’t exposing those reserved blocks.
🤔 thought of the day: the UITextView/NSTextView is probably the worst way to use the TextKit 2 framework to the fullest. many artificial limits put on the API or internal assumptions.
also the late hierarchical additions to NSTextElement (parent, childElements) is solely to support specific implementation details and in my opinion shouldn't be on that level of the model. Somebody added it as “a hack" to make things work
I fixed scrolling in STTextView 0.9.2. It bugged me for a while that it was broken (not broken-broken, but the scroller's total size was not indicative). After learning one or two new things about the TextKit 2 layout behavior, I hereby report that the scrolling experience is back to normal without disturbing the overall performance.
one of my favorite aspects of iOS development is that there are 1024 flavors of MVVM, and nobody admits with a straight face that it is a Fat Model that matters
VSCode is an annoying piece of software. It shows messages that look like errors, but the message is not. So the question is whether I want to continue (what exactly?), and the possible answer is "don't show again."
@krzyzanowskim VSCode is the best Frankenstein monster software I have on my machine. Id have laughed if you were going to tell me ten years ago I’d be using an electron app that executes code with a dozen plugins from vendors I don’t know and can’t trust.