Software: Weekly Summary (November 03-9, 2025)

I’ve been poking through a week’s worth of software chatter. It’s a cozy little mess of opinions, fixes, and tools people either love or tolerate. Some posts are practical. Some are twitchy takes. Some are notes-to-self that turned into surprisingly useful lists. I would describe them as the kind of weekend reading you put down and then pick up again because a line stuck with you.

PDFs and the kind of small wars they start

PDFs show up like socks in a laundry pile. Everyone has strong feelings. AppAddict wrote about that this week. The post is called “People Sure Are Picky About PDF Tools.” It walks through the usual suspects: Adobe Acrobat Pro, macOS Preview, free web tools, and a handful of paid apps. The tone is: most people don’t need the big gun. To me, it feels like a friend saying, “Stop buying the fancy blender if you just make smoothies.” They point out the basics people want — annotation, form filling, moving pages, basic security — and how many free or cheap tools handle that. But then, as expected, the pros still exist. There are features you only get from paid apps, especially when you need reliable OCR, batch processing, or Windows/mac parity. The post also notes how the Mac versions of some apps are weaker than their Windows counterparts. That old cross-platform ache keeps cropping up.

A thing that stuck: the microscopic habits people have around PDFs. One commenter’s workflow is glued to Preview. Another would die for a consistent batch tool. It’s like watching two folks argue whether you should bake bread in a Dutch oven or a cast-iron pan. Both work. Both have rituals.

Photos: Apple’s limits and useful add-ons

Photos on macOS is a recurring tug-of-war. AppAddict again, but this time writing about PowerPhotos. The headline is straightforward: PowerPhotos boosts Apple Photos in ways Apple doesn’t. If you think of Photos as a comfy jacket with no pockets, PowerPhotos sews in a few deep pockets and a hidden zipper.

I’d say the most useful bits are multi-library management, real duplicate control, batch metadata edits, and smarter searching. There’s a learning curve, though. The author warns about the need to keep good backups. That’s sensible. Apple’s ecosystem makes some things easy and other things fragile. PowerPhotos is clearly for people who hit the ceiling with Photos and want to avoid building some bespoke Lightroom-like mess.

There’s a little catch: it still leans on Apple’s world. That makes it brilliant if you’re deep in macOS. It’s less attractive if you want something that lives equally well on Windows or Linux. Like choosing a second language for a family — if everyone already speaks English, learning Spanish adds local color. But if half the family speaks Mandarin, Spanish is less useful.

App lists, stacks, and the comforting chaos of “my setup” posts

This week had a few posts listing software that authors actually use. These are always oddly satisfying. They’re like peeks into someone else’s garage where every tool has a sticker and a little story.

• Relja Novović shared “My Application Software stack.” It’s a practical, categorized list: communication, productivity, security, creative apps, utilities. The post is full of small endorsements — why a particular tool stayed and why another left. That kind of list says more than it seems. It reveals priorities: reliability, minimal fuss, and sometimes a stubborn love for FOSS.

• Jana did the hardware and software round-up called “Uses.” It’s more than just a list. It’s a map of customizations: how keyboards are set up, why certain monitors got chosen, why self-hosted services exist in the first place. It reads like someone showing their toolbox and then telling you how they re-routed the wiring in the garage. Folks who tinker will enjoy it.

• blog.chay.dev threw in “My bookmarks.” Not a software stack per se, but a curated list of readings that influenced their thinking about software and engineering. These posts are useful because they’re not just what someone used last week. They’re what shaped the person’s approach.

The pattern: these posts all side-step fashionable software. They prefer things that keep working, or things that can be fixed easily. That says a lot. People are tired of shiny apps that need constant babysitting.

Native apps vs browser-based, and the Electron gripe

Lucio Bragagnolo’s post (titled roughly “Sta bene sotto tutto”) is a short, sharp jab at Electron and browser-based apps on Apple Silicon. The gist is familiar: native apps feel better, lighter, and faster on Apple chips. Electron apps, even if polished, can feel sluggish. He notes exceptions: WebAssembly brings some heavy apps into the browser in a surprisingly efficient way — like Maxima now running in the browser. That felt like a plot twist: old heavy software, trimmed and running in a tab.

I’d describe the sentiment as “native-first patience.” People still want web apps, but they want them to behave like local apps. Otherwise it’s like watching a touring band try to play a small, precise jazz set with stadium gear. It can work, but it feels off.

Compatibility nostalgia: PowerPC, ARM, and the weird ways apps keep working

There was a neat little experiment by Pierre Dandumont. He explored apps compatible with PowerPC, Intel, and Apple Silicon — those universal binaries Apple likes. He tested SD Memory Card Formatter on a PowerBook G4. The surprise: the installer didn’t run on PowerPC, but copying the app from a newer Mac still allowed it to run. That’s delightfully Mac-nerdy.

This strikes me as part archaeology, part stubbornness. People still tinker with old machines. The Mac world leaks into the past in weird ways. It’s like finding an old record player and discovering a new cartridge makes the sound fresh. There’s also a skeleton-of-compatibility idea here: sometimes apps are more flexible than installers assume.

System updates, annoyance, and the interface that trips people up

Michael J. Tsai wrote about macOS 15.7.2 and 14.8.2 updates. The post is short, factual, and a little exasperated. Security fixes are important. But the user interface around Software Update frustrates people. There were comments from readers about how selecting updates is annoyingly fiddly.

This is the perennial UI paradox: you design a system to be simpler and then the simplification hides the control people expected. It’s like rearranging a kitchen so the toaster is hidden behind a cabinet. Minimalism can be handy — until you need the toaster.

Calibre’s security fix, and why open-source matters here

Calibre 8.14 got a security patch and other small improvements. Brian Fagioli points to a remote code execution vulnerability in the FB2 input parser. That’s a serious one if you accept files from strangers. The update also improved Tolino e-reader support, language suggestions, and added a shortcut for virtual libraries.

Calibre is an interesting case study in where open-source shines. Bugs get found. Fixes get pushed. The community moves quickly when danger appears. That kind of vigilance is why people keep using software like Calibre even if the UI is a little old-school. It’s reliable in a way polished commercial apps sometimes aren’t.

The messy, emotional side of OS switching

Jack Baty’s “I may have to use macOS on the desktop” is the kind of post that hits a nerve. He tried to move from macOS to Linux and bumped into the old problem: creative apps and certain workflows just aren’t as pleasant outside Apple’s ecosystem. Photo processing is the main pain. Darktable and SilverFast are OK, but they’re not Capture One. BBEdit had no real substitute. Messages and FaceTime were also sore points.

This loops back to a recurring theme: software is more than features. It’s about expectation, smoothness, and tiny conveniences. When those vanish, the cost isn’t technical. It’s emotional and time-consuming. Jack contemplates a dual-OS setup: macOS on the desktop, Linux on the laptop. That’s like having a Sunday suit and a work hoodie. Both work. But swapping between them is a chore.

Community-built tools and the myth of single founders

In a different vein, Igor Bubelov wrote about BTC Map. The post clears up a misconception: BTC Map isn’t the product of charismatic founders. It’s a loose collective. Data contributors and coders keep it alive. No legal entity, no official founders. If you needed to contact someone, the post says, go to the public channels and ask for the data or code maintainers. It’s a good reminder that many useful digital projects are low-structure, high-effort affairs.

This is the open-source reality again. Projects live on the backs of volunteers and maintainers. The neat thing is that a useful product can exist without a corporate umbrella. The messy thing is that without that umbrella, you also get a lot of ambiguity when things break.

A little life, a little software: tangents that end up connecting

A few posts felt less explicitly about tools and more about life. Robb Knight shared “Now (November 2025)” where he writes about pink ink, birthday prep, redesigning a website, and trying some software tools. It’s small and human. The pink ink search is a charming detour. It connects oddly well with software choices. People pick tools the same way they pick pens — because they like the feel.

rwblickhan.org posted a reflective piece that starts with criticism of cultural tastes and then sidles into software mentions: chezmoi, helix editor, and a tiny color picker project. The post is less about the software itself and more about what it signals — small craft, small tools, and the joy of making something useful for oneself.

The meta-thread: people want tools that respect their time

If I had to name a recurring theme it would be this: no one wants to babysit their tools. Across posts, the same little demands show up. Folks want: reliability, speed, predictable updates, few surprises, and the ability to fix things themselves if required. Whether it’s Calibre maintaining security, PowerPhotos patching gaps in Photos, or people rolling back to macOS because the Linux app stack didn’t align — the ask is the same.

There’s also an undercurrent of platform loyalty. Apple’s ecosystem still keeps a lot of people because some workflows are buttery smooth there. But that loyalty is pragmatic. It’s not religious. If a tool is better elsewhere, people will move. They just don’t want to pay hidden costs — time, lost features, or endless fiddling.

Small disagreements and little habits

Not everything lines up. Here are a few small, repeated disagreements worth noting:

• Free vs paid PDFs: Many say free tools do the job. Others insist on paid apps for reliability and advanced features. It’s the familiar price-versus-friction tradeoff. If you do PDFs daily, the paid app looks cheaper over time. If it’s once a month, free tools win.

• Native vs web: The Electron gripes are loud. But web apps keep winning when cross-platform reach matters. So the split is pragmatic, not dogmatic.

• OS allegiance: Some are ready to live in Linux. Others are inching back to macOS. Most fall somewhere in the middle and dream of a perfect hybrid setup.

These are tiny arguments, like neighbors disagreeing about which type of bird feeder is best. They’re loud sometimes, but they don’t change anything overnight.

Practical takeaways — little hints worth following up on

If you read the full posts, you’ll find small practical things that matter. A few that stuck with me:

• Check Calibre if you handle e-books a lot, and update ASAP if you use FB2 files. The vulnerability was real.

• If you’re deep in Apple Photos but hit limits, PowerPhotos might save you time and headaches. It’s not a giant system like Lightroom, but it tucks into Photos neatly.

• If you care about app speed on Apple Silicon, favor native builds. WebAssembly can surprise you, but Electron often lags.

• If you depend on PDFs daily, think about the long-term cost of a paid tool. It might be cheaper than constant workarounds.

• If you tinker with older Macs, sometimes apps will run if you move them, even when the installer fails. Don’t expect it to be foolproof, but it can feel like pulling an old engine back to life.

Each of those is a small thread. Pull any one and you’ll find more to read.

Who seemed worried, who seemed satisfied

Worry showed up a lot around security and updates. System updates that hide details, libraries that need careful backups, and remote code execution bugs all prompt vigilance. That’s sensible. There’s also a steady satisfaction with tools that “just work” — like Calibre when it’s updated, or PowerPhotos when it finally does what you wanted Photos to do.

The most human posts are the ones that mix utility with petty annoyances. The posts that list tools feel like a friend showing you their neat shelf. The posts that rant about missing features feel like someone mid-complaint on a bus, and you nod because you’ve got the same gripe.

A note on communities and DIY software culture

A recurring, quiet celebration is of community effort. BTC Map isn’t an org with PR. It’s people adding merchants and keeping data fresh. Calibre’s patch came from code maintenance. A lot of useful software is a hobby that grew up. That’s comforting if you like the idea of control. It’s messy if you prefer a neat company and a hotline.

Relatedly: “my stack” posts show a thoughtful DIY culture. People mix open-source tools, paid subscriptions, and local scripts. It’s not raw hackerland. It’s careful mix-and-match. Kinda like a home cook who orders some spices from a specialty shop and uses frozen peas from the supermarket.

Little pedestals: choices that say something

Some choices read like a small profile. Choosing BBEdit over an editor that’s trendy. Choosing Capture One despite cost. Choosing PowerPhotos instead of migrating to another photo manager. These are minor identity markers. They show what someone values: control, clarity, or maybe habit.

It’s all very human. People choose tools because of tiny rewards: a UI that doesn’t mis-click, a shortcut that feels right, or a batch process that runs overnight. These choices aren’t glamorous. They’re the kind of thing you only notice when they’re gone.

If you want to dive deeper

Each of these posts is short enough to skim but deep enough to make a point. If you care about PDFs, read AppAddict. If you want a practical Photos add-on, look at PowerPhotos. If you’re thinking of switching OSes, Jack Baty’s story is a good honest read about costs you don’t usually count. The Calibre update is small but important. BTC Map’s note is a reminder about how many services are run by volunteers. And the various “uses” and “stack” posts are great if you like peeking under someone’s hood.

There’s a charm in the smallness of these posts. They don’t pitch anything. They mostly explain what works for their author. They leave room for disagreement. They sometimes meander — and that’s fine. The tangent about pink ink in Robb Knight’s note is a perfect example. It has nothing to do with apps, and yet it’s the kind of small preference that explains how people choose software. It’s like keeping the right pen in your pocket.

If you’re in the mood for a short rabbit hole, try the PowerPC compatibility tale or the Calibre changelog. If you want practical shopping advice, the PDF and photo posts give clear paths. If you just like seeing how other people arrange their digital life, the “uses” pieces are oddly comforting.

There’s a simple through-line here: tools that respect attention get kept. Tools that don’t are swapped out, or cursed quietly, or left uninstalled. People want to be practical. They want to spend time on the work, not the tool. That’s not radical. It’s just a good way to decide what to install and what to avoid.

So go read the original posts if something here pricked your curiosity. The full writing has the fine print and the little screenshots, and sometimes the comments are where the gold is. These posts are short doorways into bigger conversations about what software should do: help, not hassle, and maybe, occasionally, delight.