Juli Clover (release notes, no security, no enterprise, no developer):
iOS 26.2.1 adds support for the next-generation AirTag that Apple introduced today.
[…]
The update also includes unspecified bug fixes, according to Apple’s release notes.
Juli Clover:
The iOS 26.2.1 update that Apple released today further addresses an issue preventing some older mobile phones from being able to make emergency calls.
Adam Engst:
Apple claims there are also bug fixes, but doesn’t deign to clarify what they might be.
More intriguingly, the company also released updates to four older versions of iOS and iPadOS, dating back to iOS 12. The updates include:
- iOS 18.7.4 and iPadOS 18.7.4
- iOS 16.7.13 and iPadOS 16.7.13
- iOS 15.8.6 and iPadOS 15.8.6
- iOS 12.5.8
Usually, when Apple updates much older operating systems, it’s because of a particularly problematic security vulnerability, though even then, the company seldom goes back more than two releases. However, something else is going on this time, as indicated by the security notes, which state that none of the releases have any published CVE entries.
Apple seems to be doubling down on encouraging users to update to iOS 26. These bug fix updates for iOS 18 and earlier are only available for users with older iPhones. If your phone can run iOS 26, you have to update to it or be stuck with known security vulnerabilities.
Previously:
AirTag Australia iOS iOS 26 iOS Release iPhone 12 Security
Juli Clover (no release notes, no security, no developer):
Today’s update enables Precision Finding for the new AirTag 2 on the Apple Watch Series 9 and later and the Apple Watch Ultra 2 and later. Prior to now, Precision Finding for the AirTag has been limited to the iPhone.
It is not yet clear if the update enables Precision Finding on Apple Watch for the original AirTag, or if this is a feature limited to the new AirTag 2.
Previously:
AirTag watchOS watchOS 26 watchOS Release
Ben Cohen:
A sequence provides access to its elements through an Iterator,
and an iterator’s next() operation returns an Element?.
For a sequence of noncopyable elements, this operation could only
be implemented by consuming the elements of the iterated sequence,
with the for loop taking ownership of the elements individually.
While consuming iteration is sometimes what you want, borrowing iteration is
equally important, serves as a better default for noncopyable elements,
and yet cannot be supported by the existing Sequence.
[…]
Instead of offering up individual elements via next() as IteratorProtocol does,
BorrowingIteratorProtocol offers up spans of elements. The iterator indicates there
are no more elements to iterate by returning an empty Span.
[…]
Note that in the case of Array, the new protocol results in much less overhead
for the optimizer to eliminate. Iterating a Span in the inner loop is a lot
closer to the “ideal” model of advancing a pointer over a buffer and accessing
the elements directly. It is therefore expected that this design will result
in better performance in some cases where today the optimizer is unable
to eliminate the overhead of Swift’s Array.
[…]
For this reason, it may not be appropriate to switch all for iteration to use
BorrowingSequence when Sequence is available. How to determine which cases are
better (such as Array is expected to be) and which are worse (such as the UnfoldSequence
example above) needs further investigation. […] For now, if a Sequence conformance is available, it will be used
even if BorrowingSequence is also available.
I haven’t had a need for noncopyable types, but I’m interested in reducing ARC overhead when traversing objects. Most of the time I don’t actually need to retain and release an object just to look at it briefly because I know that it’s not going to be removed from the collection.
Previously:
Automatic Reference Counting (ARC) Language Design Memory Management Optimization Programming Swift Programming Language
Jan Tångring (Hacker News):
“AI slop and bad reports in general have been increasing even more lately, so we have to try to brake the flood in order not to drown”, says cURL maintainer Daniel Stenberg to Swedish electronics industry news site etn.se.
Therefore, cURL is terminating the bounty payouts as of the end of January.
[…]
Not all AI-generated bug reports are nonsense. It’s not possible to determine the exact share, but Daniel Stenberg knows of more than a hundred good AI assisted reports that led to corrections.
curl (Hacker News):
We will ban you and ridicule you in public if you waste our time on crap reports.
Previously:
Artificial Intelligence curl Open-source Software Programming Security
