Software: Weekly Summary (December 08-14, 2025)

There’s a lot of small, sharp thinking in the feeds this week. The posts don’t all shout the same message, but a few threads keep popping up — ownership, friction, small tools doing one job well, and a low-key worry about things drifting away: licenses, old file formats, and how we glue our little workflows together. I’d say it feels like people tidying their own sheds and then writing down where they put the hammer.

Licensing, accidents, and what "open" really means

Kerrick Long pokes at a single product and finds a tangle. The piece about Writebook and 37Signals reads like someone reading the fine print in a secondhand car ad. The ONCE License Agreement sits next to an MIT clause. One looks like a gentle gatekeeper, the other like an open door. Kerrick asks: did the maintainers accidentally leave the door open? It’s not dry legalism. It’s more like: can you promise people freedom and then quietly box it back up?

I would describe the situation as one of those kitchen-sink moments. You mean to hand someone a spoon, and you give them the whole drawer. To me, it feels like a slow-motion oops that matters, because a slip between licensing words changes whether a tool becomes something many people can build on, or stays a tightly wrapped feature for a single company.

That tension shows up again and again in other posts this week. There’s that same itch for control, for knowing what you can do with your tools, whether you can tweak them, share them, or take them apart. It’s not abstract. People are worried about that door being open or closed.

Small tools, tight workarounds: the joy of tiny workflows

Two separate notes talk about doing one thing well.

AppAddict and Amerpie by Lou Plummer both ran near-identical takes about PhotoSweeper. Funny to see two voices land on almost the same sentence at the same time. PhotoSweeper is praised for being a dedicated duplicate photo finder on macOS. It’s the kind of app that does not try to be a full photo manager. It’s simpler: find duplicates, offer safe deletion, support a long list of formats. I’d say it behaves like a trustworthy neighbour who will help you carry heavy cases to the car but won’t offer to redecorate your living room.

The appeal is obvious. Many of us have phone photos, DSLR backups, and a handful of edited versions for the same shot. PhotoSweeper doesn’t pretend to be Photoshop. It just hunts duplicates, and it does that fast. Both posts note it’s a one-time purchase — that little thing matters. It’s like preferring to pay cash for a good tool rather than sign up for a subscription that nags you forever.

Then there’s Thomas Countz, who writes about a tiny but elegant programming trick. He introduces a custom Forth word called 'go' that clears old definitions and opens a project file in Vim for editing. That core idea — edit, reload, repeat — is nearly universal. In other ecosystems people use hot reload, live previews, or file watchers. Thomas’s 'go' is old-school and clever. It’s like setting your coffee pot to keep the brew at the right heat: simple, reliable, and you notice it when it works.

Forth is niche, sure, but the note is about cadence more than language. A tight edit-reload loop makes building feel like tapping along to music. The tool removes a tiny bit of friction, and suddenly you’re productive. That’s a recurring theme. Folks are re-finding that small comfort: a single button or command that gets the job done.

App defaults and the comfort of routines

Three authors list what they actually use every day.

Ruben Schade lays out a mixed bag: 3D tools, backup choices, browsers, music apps, and productivity helpers. He flips between open-source and self-hosted options and the odd commercial tool. It reads like someone showing you their toolbox after a weekend of garage work.

Luke Harris does the same, offering his app defaults for 2025. He keeps some long-standing favourites — NetNewsWire for RSS, Apple Mail for emails — but he also swaps out editors and terminals. The point isn’t novelty. The point is what fits right now. These choices are relationships, not badges: people keep what gets them through the task.

Gonçalo Valério is more explicit about freedom and alternatives. He lists lesser-known apps that respect user choice: Skanlite, Strawberry Music Player, DBeaver, Spectacle, QOwnNotes. This one felt like a tour of quiet rebels. I would describe them as the kinds of tools you find when you’re past the mainstream and looking for something that won’t sell your soul or rope you into a subscription. To me, it feels like walking into a small indie shop after too many chain stores.

There’s a pattern here. People aren’t chasing the flashiest app. They’re chasing fit. They want tools that don’t fuss, that they can tweak, or that don’t lock them out. It’s less about novelty and more about comfort and control. These app lists are small confessions of what works, and why.

Raycast, the Swiss Army knife everyone’s stealing features from

Amerpie by Lou Plummer also writes a practical piece on Raycast. They’ve used it a lot and show how it replaced a string of apps for them. Raycast is being treated like a kitchen knife that learned to be a screwdriver too: it aggregates commands, offers extensions, and makes you reach less for the mouse.

It isn’t just about saving time. It’s about reducing context switches. The post lists specific apps Raycast has replaced, which is enlightening — because you realise how many little interactions you had with separate apps. Raycast bundles them. I’d say this is where convenience meets consolidation. Some people will cheer that. Some will worry that centralisation makes a single point-of-failure.

This connects to the licensing point. When one tool becomes a hub, what licence does it carry? Who decides what it can or can’t do? That earlier tangle around Writebook feels relevant again.

Tool building and ownership — indie tools, personal projects, and playfulness

Juha-Matti Santala has a very personal voice. They say they’re a tool builder at heart and love building within the IndieWeb community. The key note is ownership: control over your data and content. The post mentions non-commercial, personalized solutions and a neat idea to support a Pokémon bingo race — a small tool to structure a fun event. It’s playful and purposeful.

To me, it feels like the groove many hobbyist builders live in: they make tools to enable something they want to do. The pleasure isn’t merely the code. It’s the orchestration. It’s like someone building a little cart so their neighbour can carry bags to the market faster.

And there’s honesty: the author prefers making the things that hold things together rather than being the one in the spotlight. That attitude filters into other posts too. They’re not out to build unicorns. They’re out to reduce friction, to make some tasks gentler.

Saving dusty formats and nostalgia for old tools

Dave Pearson writes about Norton Guide files and what happens when old corners of computing go dark. He digs through the DOS-era archive, finds tools he made for reading those files, and worries that knowledge is evaporating as sites shut down. So he builds a new site to publish a collection, and asks for permissions and contributions.

This felt quietly urgent. It’s not trendy. It’s not about shiny new things. It’s preservation. It’s like finding an old family recipe and deciding to keep it alive because otherwise nobody will make it again. The post echoes that theme of ownership and guardianship seen elsewhere. If we don’t preserve these small things, they vanish — and with them the context and practices they carried.

There’s a mild sadness in this week’s reading: people are doing the quiet, important work to keep old knowledge from being lost. They build small archives, publish, and ask the community to help. That’s the kind of civic-minded elbow grease that doesn’t make headlines but matters.

Hardware, games, and a sideways glance at AI-driven markets

Jason Coles delivers a newsletter that mixes gadget talk and personal notes. He covers the ASUS ROG Flow Z13, shares impressions of the Game Awards 2025, and notes that RAM prices are on the rise due to AI demand. That last note is a small but significant pattern you’ll find in tech chatter these days: AI doesn’t only live in code; it changes supply chains.

It’s a reminder that software sits on top of hardware markets and global demand. When model training needs lots of memory, regular users bump up against price effects. The newsletter is slightly gossipy, a bit like swapping notes at the pub about the latest PC build, and it earns its keep by connecting individual experiences to broader market trends.

The practical: Android Studio and the developer toolkit

Nacho Morató offers a solid guide to Android Studio. The write-up is thorough about what the IDE is, its history, and why it matters. For devs, it’s less of a manifesto and more like a practical map: what to expect, what features matter, and why it’s still the mainstay for Android development.

There’s comfort in tools that are this well-formed. Android Studio has an entire ecosystem wrapped around it: debuggers, emulators, profilers. If you need a one-stop shop for building Android apps, it’s the place. To me, it feels like the difference between buying a single Swiss watch and assembling a watch from pieces.

If you’re curious, the guide is worth a read for the specifics. It’s good primer material for someone crossing into Android from other platforms. And it connects to the wider theme: people want toolchains that do the heavy lifting so they can focus on the part they care about — the app, the feature, the experience.

Repetition and echoes: patterns that matter

Several motifs come through when the posts get read together.

• Ownership and licensing: Kerrick’s Writebook piece sits next to Juha-Matti’s IndieWeb piece. Both are different angles on control — one legal, one philosophical. The debate around who owns what keeps circling back.

• Small, sharp tools vs. behemoths: PhotoSweeper, Thomas’s 'go' in Forth, and the app lists from Gonçalo, Ruben, and Luke all celebrate small, focused tools. People want things that don’t do everything, but do the thing they need reliably.

• Preservation and memory: Dave Pearson’s Norton Guide rescue mission reminds us that software culture has a history worth keeping. Old formats and old knowledge don’t survive on autopilot.

• Consolidation and hubs: Raycast and the push to consolidate tasks into one launcher show the other side — a lure toward centralisation because it reduces context switching. But centralisation brings its own trade-offs.

• The market’s invisible hands: Jason’s note about RAM prices shows how software trends influence hardware economics. That ripple matters to everyday users and hobbyist devs alike.

There’s a certain tone across the posts. People are practical. They’re tired of flash. They want things that work and that they can reason about. Some have the patience to hack things together. Some want to pick reasonable defaults and move on. That spectrum — tinkerers to pragmatists — is visible everywhere.

Small ideas that make a big difference

A few posts offered tiny, repeatable tricks. They’re the kind of things you’d scribble on a sticky note and keep on your monitor.

• Use a single-purpose duplicate finder if you have a bloated photo library. It’s less risky than wrestling with a full photo manager. PhotoSweeper seems to be the quiet clinic for that.

• Build a short edit-reload loop. Thomas’s 'go' in Forth shows how a tiny command can change the rhythm of coding. That’s portable: most languages and setups benefit from shortening the feedback cycle.

• Keep a list of app defaults and revisit them occasionally. Luke and Ruben show that switching one or two tools can reshape your day. If your editor or terminal is slow or awkward, it’s worth changing.

• Preserve old formats if you care about history. Dave’s project to gather Norton Guides is a reminder that if you care, you might be the only one doing the archiving.

These are small, practical things. They don’t require startups or VC. They require time, and a bit of care.

Where the disagreements hide

There weren’t huge arguments this week. But tensions exist in subtext.

• Open vs closed: Kerrick’s legal reading raises questions about intent. If a license appears permissive, was that intended? The post doesn’t scream; it nudges. But even a nudge prompts discussion about vendor intent and community expectations.

• Centralisation vs dispersion: Raycast fans like one interface to rule them all. Others prefer separate small apps they can change or replace. Both positions make sense. One values speed, the other values modularity.

• Preservation vs progress: Dave’s archival impulse sits against the forward push to new file formats and services. Do you keep the past alive at all cost, or let it fade and focus on what’s next? The posts don’t pick a fight, but they show both instincts in people who write about software.

Little tangents that are pleasant to follow

There are some small, charming bits spread across posts. Juha-Matti’s Pokémon bingo idea is a delightful detour. It’s the kind of personal project that reveals where passion lives — not in making the next big thing, but in making a small thing that helps people play better. It’s a human moment in a sea of workflow talk.

Gonçalo’s list of apps reads like a late-night browser tab crawl — you start with one mainstream app and then go hunting for alternatives. That’s how people discover new tools: curiosity and a willingness to try a smaller shop.

And the two PhotoSweeper posts, almost mirror articles from two different writers, make a meta-point: when a tool fills a clear need, voices converge. It’s like when two neighbours recommend the same baker.

Where to dig deeper

If your curiosity is piqued, the posts reward a visit. Kerrick’s piece is the kind you read if you care about licensing details and the practical consequences. Thomas’s Forth note is short but useful if you like tight developer loops. PhotoSweeper reviews are practical for anyone with too many photos. Dave’s archival work is for archivists, nostalgia buffs, and anyone who likes rescue missions. Raycast and Android Studio pieces are good roadmaps if you want to switch workflow or learn how major dev tools fit together.

The authors write with different voices. Some are technical and direct, others are more playful. That itself is instructive. Read them in sequence and you’ll feel the week’s mood: cautious, practical, and quietly inventive.

If you like small victories in software — shaving seconds off a workflow, keeping a format alive, choosing a one-time purchase over subscription — there’s a lot to pick through. The posts won’t hand you a manifesto. They hand you tools, warnings, and recipes. Pick the ones that feel like your toolbox.

So, browse a few of the links. See what makes you nod, what makes you bristle, what makes you want to write your own sticky note for the next time you sit down to work. There’s a steady hum under these posts: people building, preserving, and choosing — over and over, choosing the things that make their days less fiddly.