News for hackers. Stuff that matters.

stevekerr

I like heuristics, but find broad statements are usually a bad idea in IT/Software. Developers in particular are very quick to find holes in logic.

When I think of code, I like to compare it to old complex physical machines. Think automaton. If you zoom in enough, what you see is indeed somewhat simple. But zoom out and the answer changes.

Then there is maintenance, manufacturing, tooling, etc.

I suspect that as humans living in a physical world, we understand intuitively the vast knowledge and skills required to design and build different kinds of machines. Software tends to hide inside boxes that look similar, but are infinitely variable.

Re:As a Windows user, it's a surreal way to install a program on Saturday August 08, 2026 @02:20AM (#49219326)
That makes a lot of sense. With the icon method: The user is in full control.

In our case, the CLI is part of a data sync system, so it does need a "special" once-per-hour check for new data (keeping local and mobile in sync).

I've actually been surprised how strict Apple is before it will happily let signed code run. But the average user (including me previously) doesn't know that. I think trust comes down to being clear up front.

Note to self: Add extra details/options to installer (WYSIWYG)

Re:As a Windows user, it's a surreal way to install a program on Saturday August 08, 2026 @01:51AM (#49219206)
Why not .pkg (next, next, installer)? For the past week, I've been tweaking my startup's CLI to install as a .pkg, satisfy Apple signing, and everything that goes along with that. I've often wondered why so many companies opt for the icon method.