Malcolm Owen:
Bungie has finally brought all of the “Marathon” trilogy of games to Steam, with “Marathon Infinity” now playable for free on modern Macs.
[…]
Classic Marathon Infinity is a free game on the Steam storefront, playable on both Mac and Windows PC. It is a faithful re-release of the 1995 first-person shooter, using the original data files, but modernized.
These modernizations include widescreen HUD support, 3D filtering, positional audio, and 60+ fps interpolation, all under the Aleph One game engine.
Previously:
Bungie Game History Mac Mac App macOS 14 Sonoma Marathon Steam
Toomas Vahter:
This function works as a one shot function and the onChange closure is called only once. Note that it is called before the value has actually changed. If we want to get the changed value, we would need to read the value on the next run loop cycle. It would be much more useful if we could use this function in a way where we could have an observation token and as long as it is set, the observation is active. Here is the function with cancellation support.
[…]
The token closure controls if the change should be handled and if we need to continue tracking. Will and did change are closures called before and after the value has changed.
Previously:
Update (2024-09-18): See also: Marcin Krzyzanowski.
iOS iOS 17 Mac macOS 14 Sonoma Programming Swift Programming Language SwiftUI
Wade Tregaskis:
If any view in the [active] window contains a Toggle – even one that’s disabled or hidden – then Continuity Camera (re. ImportFromDevicesCommands and importableFromServices) doesn’t work; all the submenu items under “Import from iPhone or iPad” are disabled.
I don’t know if this is truly specific to Toggle, that’s just the example case I happen to have isolated [first?].
What’s really weird is that once a Toggle has ever been displayed, even if you subsequently remove it from the view hierarchy entirely the “Import from iPhone or iPad” submenu items all remain disabled.
Previously:
Bug Continuity Mac macOS 14 Sonoma Programming SwiftUI
Jeff Johnson (Reddit):
I took packet traces of the DNS queries with the firewall enabled and disabled. What I found is that the DNS query response packet consistently arrives in under 20 milliseconds after the query packet is sent, regardless of whether the firewall is enabled. Thus, it appears that the extra query time added by the firewall is caused by on-device processing of the packets rather than by any network issue.
[…]
On my MacBook Pro running Sonoma, but not on my Mac mini running Sonoma, I frequently experience a bizarre issue where the dig command takes over 5 seconds to complete when the firewall is enabled.
DNS queries are several times slower, however this may be fixed in Sequoia.
Domain Name System (DNS) Firewall Mac macOS 11.0 Big Sur macOS 12 Monterey macOS 13 Ventura macOS 14 Sonoma macOS 15 Sequoia Networking
