That wouldn't seem reproducible if the content at those URLs changes. (Er, unless it was all web.archive.org URLs or something.)

This is a problem with the Web. It should be easier to download content like it was updating a git Repo.

I'll third it. I've started to see more and more cargo culting of "fixes" that I'm extremely suspicious do nothing aside from making the code bulkier.

They’ve had Reduce Transparency (under Accessibility) for a long time now. It still works.

Background Assets have existed for years. I’m not sure that 200GB figure is new.

Which ones would you like to get rid of?

I can hear the whooshing sound accompanying the snark... I'm talking about how this is communicated. I'd suggest that Apple say something like "200+ developer frameworks" rather than counting up the number of individual methods or functions.

Here is a summarization provided by Claude after I back-and-forthed it a bit:

--

Apple Developer Frameworks

This list represents the vast ecosystem of frameworks available to developers for building applications across Apple's platforms.

I. Foundational Frameworks

These provide the fundamental services and data management capabilities for all applications.

- Core Frameworks: Essential for data types, collections, and low-level services. Examples: Foundation, Core Data, Core Foundation

- Security: Manages user authentication, authorization, and cryptographic services. Examples: CryptoKit, LocalAuthentication, Security

- App Services: Supports core application functionalities and integrations. Examples: Contacts, EventKit, StoreKit, WeatherKit, ClockKit

II. User Interface & Experience

Frameworks for building the visual elements and user interactions of an application.

- UI Frameworks: The primary toolkits for constructing user interfaces. Examples: SwiftUI, UIKit (for iOS/tvOS), AppKit (for macOS)

- Services: Provides access to system-level services with a UI component. Examples: MapKit, CloudKit, Core Location, PassKit

III. Graphics & Media

For creating rich visual content, games, and handling audio/video.

- Graphics & Games: High-performance 2D and 3D graphics rendering and game development. Examples: Metal, SpriteKit, SceneKit, RealityKit

- Media: Manages the playback and processing of audio and video. Examples: AVFoundation, Core Audio, VisionKit

IV. Machine Learning

Enables the integration of intelligent features into applications.

- Core ML & Vision: The foundation for machine learning models and computer vision tasks. Examples: Core ML, Vision, Natural Language, Speech

- V. Platform-Specific Frameworks

The number of available frameworks varies significantly across Apple's operating systems, reflecting the unique capabilities of each platform.

- macOS: ~250+ frameworks

- iOS/iPadOS: ~200+ frameworks

- watchOS: ~50-60 frameworks

- tvOS: ~35-40 frameworks

- visionOS: A growing set of frameworks for spatial computing.

Best guess: that's because no organizations are writing their first PL/I apps in 2025; and there aren't many PL/I-using organizations who weren't big IBM customers, who largely migrated from OS/2 to Linux. So I wouldn't be shocked if a Windows version wouldn't bring in enough money to make even a relatively easy port worth it.

Next-to-best guess: author was an OS/2-head, many of whom have been hating M$ Windoze for 30 years at this point! Ah, those were good days.

> So I wouldn't be shocked if a Windows version wouldn't bring in enough money to make even a relatively easy port worth it.

True, but I’m sceptical the Linux or OS/2 versions have ever brought in any money either.

This looks to me suspiciously like a hobby project masquerading as a commercial venture

They just feel like yet more KPI-demanded clutter.

And those are also all things that a smartphone can do (often a little worse, admittedly). Which you'll have with you anyway because of all the things it does much better than glasses can and likely ever could.

That seems like a weird way to measure it in an age of streaming TV.

That's the only part I don't like about the Switch OS, and, yes, it's very bad. And it always baffles me why they wouldn't improve the app that generates revenue of all things.