Apple: Weekly Summary (December 29 - January 04, 2026)

This week’s little patchwork of posts about Apple felt like walking through a flea market where every stall sells something familiar but slightly different. Some stalls had old radios, some had newfangled gizmos, and a few sellers were arguing about who gets to run the fair. I would describe them as connected by a few repeating threads: history and repair, control and money, design and user freedom, and the slow creep of machine learning into everything. To me, it feels like Apple is both a museum and a sandbox right now — part nostalgia, part careful chess game, part slow drift toward an iPhone-first world.

Vintage machines, stubborn problems

There’s a great hands-on repair story from Doug about a Macintosh Performa 450 that wouldn’t boot. The piece reads like a detective story with a soldering iron. The machine refused to start, but the old ROM diagnostics — the kind of thing most folks now treat as curiosities — spoke up and pointed at a RAM fault. The author traced that fault to capacitor leakage and then to a broken PCB trace. A bodge wire later, and the old Mac lives again.

I’d say this post is more than nostalgia. It’s a small argument for the usefulness of techniques that predate the cloud and sealed-unibody thinking. It’s like finding a lost key under the doormat; not glamorous, but it sure gets the door open. The diagnostic ROM became the hero. To me, that feels like a reminder: sometimes the tools that feel obsolete still do the job better than new ones. There’s a kind of charm in those ROM screens — sterile, monochrome, but honest. They don't promise the moon and then quietly mine your personal life.

If you like the smell of solder and small triumphs over flaky hardware, go read the repair log. It’s the kind of post that makes you want to open a dusty electronics box you promised you’d never touch again.

A veteran voice on expandability and mistakes

Then there’s a revisit to older times: an interview with Steve Wozniak from the mid-1980s, surfaced by John Paul Wohlscheid. Woz talks about Apple’s early missteps, especially around the Macintosh. He criticizes lack of expandability and laments design choices that boxed users in. There’s also reflection on Steve Jobs, on why Woz left, and on what real innovation should look like.

I would describe Woz’s view as a kind of patient, engineer’s disappointment. He’s less interested in showmanship and more in letting people tinker. To me, it feels like he’s warning against the kind of polished prison that looks great but doesn’t let you add a card or change something without a special tool. He argues — plainly — that machines should be more adaptable. That’s an argument you keep hearing in the background of many of these posts.

Woz’s perspective reads like advice from an older neighbor who fixed radios and rewired the house pegs himself. It’s not nostalgic for the sake of nostalgia. It’s practical: expandability lets you reuse and repurpose. If that idea feels quaint, maybe it shouldn’t.

Apple and the cautious AI play

Two posts from Philipp Dubach — yes, it appears twice in the dataset, which honestly felt like reading the same paragraph twice while drinking coffee — talk about Apple’s AI strategy. The gist: Apple is playing the long game. They’re not throwing money at building the biggest models right this second. Instead, Apple leans on distribution, device integration, and a vast installed base.

I’d say the argument is that Apple’s strength isn’t cutting-edge model-building but being an ecosystem that can sprinkle useful AI into places users actually touch: keyboards, cameras, the privacy bits, Siri, maybe even the Vision Pro. To me, it feels like watching a cautious horse at the racetrack. The horse might not be the flashiest sprinter, but it’s well-fed, steady, and has a strong owner who can bet big later.

There’s a comfort in that view if you dislike the wild west of AI startups. Apple’s cash pile gives it patience. But the flip side is obvious: sometimes the slow, careful company misses the moment when the new thing becomes defining. If you’re a gambler, Apple’s play might feel like waiting for soup to cool while the table across the room eats spicy noodles and becomes the talk of the night.

The doubled posting also nudges a small meta-point: some ideas this week felt like echoes. The same idea, repeated, gains weight — or becomes background noise. Take that as a heads-up; maybe head to the original to see if you like the tone.

Control, fees, and the courtroom shuffle

Legal and developer-facing drama shows up in Michael J. Tsai’s write-up on the appeals court decision about Apple charging a commission on external purchases. The court said Apple can charge a “reasonable” commission for external purchases made through iOS apps. But Apple can’t just start charging right away — the case goes back to district court to figure the fees.

It’s a little like telling a landlord they can ask for a pet deposit, but first they have to show it’s not punishing tenants. The ruling lets Apple keep some control over how developers present external links versus in-app purchases. But it also calls out Apple for acting badly before — there’s a finding about bad faith in not complying with an injunction. That’s the part that smells a bit like being told off in front of the neighbourhood.

I would describe this as a middle-of-the-road outcome. It neither blows wide open the app store rules nor slaps Apple so hard it becomes a free-for-all. To me, it feels like the legal system nudging the balance: Apple keeps control, developers get a sliver more breathing room, but the overall power dynamics barely budge. If you’re a developer, read Tsai’s piece — it’s the kind of thing that affects whether you feel you’re building on firm ground or on quicksand.

A small side note: the ruling lands near Epic’s return to Google Play after a settlement with Google. That’s like seeing two neighbours resolve their shouting match and both go back to mowing their lawns. Important, but also... everyday.

Screens, sizes, and measuring things that matter

Lucio Bragagnolo posted a neat, practical rundown of screen sizes across Apple devices. It lists iPhone, iPad, iPod touch, Apple Watch, Vision Pro, and Apple TV sizes. Why does this matter? Because a surprising number of complaints and confusions start with the wrong idea about scale. Lucio reminds readers that knowing the spec can avoid basic mistakes.

I’d say the post is for the useful, slightly nerdy kind of person who likes to know which sleeve fits which device. To me, it feels like checking your luggage dimensions before you fly: boring, but when you do it right, it saves you a headache at the gate. Lucio even throws in a literary quote about time passing and hopes for the new year. It’s a small, human touch. I liked that.

The desktop loses its edge: a bite of the forbidden fruit

Now to the sharper piece from shreyan. The post argues macOS is getting too much like iOS. The language is angry in a careful way. The argument says Apple is blurring desktop and mobile in a way that favors consumption over creation. The Vision Pro gets called out as a “consumption-centric” gadget. The post worries users are losing power — real capabilities to tinker, to modify, to go deeper — and being nudged into a passive mode of computing.

I would describe this as a really clear-headed frustration. To me, it feels like watching your local cinema turn into a giant streaming room where you can only press play and never change the seating. The critique is not just nostalgia for menus and windows. It’s about agency. When the desktop is tidy and limited in ways meant to simplify, it can also be limiting in ways that stop creative work.

There’s a connection here to Woz’s comments about expandability. Both pieces — from a different era, different voice — are saying the same thing: don’t box people in. That repetition matters. It keeps showing up in different tones: historical, technical, moral.

Privacy signals and alarm fatigue

Jamie Lord writes about Apple’s green dot privacy indicator for camera access. It’s supposed to reassure, but instead it sometimes causes anxiety. The author points out that frequent, routine alerts produce alarm fatigue. When the light goes off for a thousand tiny things, people stop checking. That’s the paradox: a system designed to warn can erode trust if it warns too much.

I’d say the privacy dot is a bit like a kitchen smoke alarm that goes off every time you toast bread. If it screams at every little thing, you learn to ignore it. To me, it feels like a small lesson from aviation: safety systems work because they’re tuned, not because they blare constantly. The piece suggests smartphone indicators should distinguish between routine, expected operations and actual suspicious behaviour.

There’s a neat crossover here with the legal fee story and the macOS critique. All three touch on how systems meant to protect users can be either genuinely empowering or just a comforting theatre. If it’s theatre, users feel safer but are actually more vulnerable.

A few things that keep showing up

• Control vs. freedom. This is almost the soundtrack of the week. Developers and users keep bumping into Apple’s appetite for control: the App Store rules, the sealed devices, the curated UI. Woz, shreyan, and Tsai’s legal summary all point in that direction from different angles.

• Caution vs. risk. Apple’s AI strategy is cautious. That might be steady, but it might also mean missing a cultural moment. The doubled AI post felt like a gentle drumbeat reminding us Apple is choosing its moments.

• User empowerment vs. curated comfort. Repair tales and expandability arguments champion tinkering and agency. The macOS and Vision Pro critiques warn we might be trading capability for slickness.

• Trust and signaling. The green dot debate shows how small design choices can erode trust if they’re not tuned properly. Signaling matters. A lot.

You’ll notice these themes come back, again and again. It’s a bit like hearing the same chorus in different songs: the melody changes, but the core keeps looping.

What felt new and what felt familiar

The repair story and Wozniak’s reflections felt familiar and grounding. They remind us that technical competence, repair, and expandability are evergreen topics. The AI pieces felt like a slow burn: not breaking news, but a steady thesis that Apple will move carefully, and maybe too carefully for some.

The legal ruling and the privacy indicator piece were more urgent. They speak to day-to-day realities: whether an app developer can survive and whether you actually notice a camera alert. These are practical things. They affect people now, more than twenty-year strategic bets.

Design criticism — the macOS convergence argument — felt like it struck a nerve. It’s the kind of piece that makes you nod and then feel annoyed at the thing you use every day. There’s a little sting to it; that’s probably why it’s worth reading.

Small digressions that connect back

I kept thinking of my grandmother’s old radio while reading the repair post. Folk puzzled with knobs and a sense of ownership. That ties to Woz’s point: when you can take the thing apart, you keep it longer. It matters. The green dot piece made me picture a smoke alarm over a toaster; small signals should be meaningful, not constant. The court ruling made me think of neighborhood rules about hedges and fences — messy, but they shape the whole block.

These might sound like tiny detours. But they’re helpful. They make the big themes feel more like everyday choices: what gadget do you buy, how much control do you want, how much trust do you place in a glowing dot.

If you’re curious to go deeper

• Read the repair account by Doug if you like practical debugging and the satisfaction of fixing something ancient.
• The Woz interview via John Paul Wohlscheid is worth a slow read if you like historical perspective with a clear lesson about adaptability.
• Philipp Dubach’s AI pieces are quick to the point: Apple is playing it safe and might benefit from time, or might miss the party. That’s a take worth thinking about as AI features roll into devices.
• Michael J. Tsai explains the appeals court decision with the kind of legal detail that answers the “what now?” question for developers.
• Lucio Bragagnolo keeps it practical with screen sizes. Handy if you’re buying a case or measuring up a stand.
• shreyan throws a sharper brick: macOS is losing what's useful to the person who makes things. That one makes you sit up.
• Jamie Lord uses aviation as a comparison to talk about alert fatigue on phones. It’s a small piece with a practical point: tune your warnings.

If you like a little variety with a through-line, this week’s posts give you it. They’re like a dinner party where one guest talks about how they fixed their car, another about how the city plans a new bridge, and a third about whether we’re all about to switch to e-bikes. Different details, same neighborhood. If any of these tiny conversations prick your curiosity, follow the links and read the original posts — you’ll find more color and the real voices behind these short summaries.

There’s a lingering question that ties most of these pieces together: how do you balance safety, polish, and profit against the messy, human desire to take things apart and make them yours? That question doesn’t have a neat answer. It keeps popping up, and not in a good way. But it does make for interesting reading, and frankly, I’m glad people are still asking it.