Good Tools Are Invisible: Why Your Favorite Editor Might Be Holding You Back

Ginger Bill, creator of the Odin programming language, published an essay arguing that quality tools should fade into the background during use. The Hacker News discussion that followed became a spirited debate about Vim, multiple cursors, and whether productivity can be measured at all.

The Core Argument

Bill's thesis is straightforward: a tool is good when you forget you're using it. The friction of working around limitations should not be celebrated as "fun" or treated as evidence that the tool is great.

From the article:

I've had people tell me how "fun" it was to build a macro to handle some one-off text-refactoring problem. But when I looked at what they were doing and how long it took, my honest reaction was: I could have done that in Sublime in a minute with multiple cursors, or just written a quick script.

The essay targets several developer habits:

• Identity over merit: Tool choices become tribal markers. When users invest identity in a tool, they defend its flaws instead of acknowledging them.
• Feeling productive vs. being productive: Solving complex workarounds can feel heroic without delivering genuine time savings. "The honest test isn't how engaged or clever you felt, it's wall-clock time."
• Learning curves as virtues: Steep learning requirements are costs, not benefits. Sunk-cost fallacy leads users to rationalize lengthy mastery periods.

Bill has used Sublime Text for 15 years and specifically praises multiple cursors as more practical than macros for most editing tasks.

What HN Is Saying

The thread split into predictable camps, but with some interesting nuance.

Pushback on the Vim framing: One commenter wrote: "It's weird how much the author fixates on Vim being 'visible' and implies multiple cursors and features in Sublime aren't. Just because your brain is trained to not think about it anymore doesn't make it any less visible."

The Vim defense: Multiple commenters pushed back on the claim that macros are inferior to multiple cursors. One noted: "I'm not sure I've ever heard anyone describe vim as a puzzle that's fun to solve. The most common sentiment is that it has a learning curve, but ends up being worth it."

Bill's clarification: The author showed up in the thread to clarify: "I used vim macros specifically as an example, not Vim as a whole... If you can effectively use vim macros, then GREAT! But if you cannot, even with using vim for decades, then please don't advertise them as the 'fun' part."

The feedback loop argument: Bill expanded on why he prefers multiple cursors: "With multiple cursors, I am seeing instant visual feedback on all instances of the cursor at once. I am getting literally 2D spatial information, compared to the 1D spatial information per each replay. The multiple cursors approach is better not because it's a different mindset, but it produces a different feedback loop to correct mistakes."

Counterpoint on power tools: A thoughtful response came from a commenter who noted: "Both vim and emacs (which have the steep learning curve) are aimed at power users. It's best to compare them to professional tools like CAD, DAW, industrial appliances... After a while, it becomes like an extension of your thinking and the tool disappears."

The LLM angle: One commenter connected the thesis to current AI tooling: "I would love for things like LLMs to be way more out of your way, more 'invisible', more tool-like. I hate the current UX of having to tame a patronizing, annoying fake human just to get things done the way I want them to be done."

The Invisible Tool Test

What tools actually pass the "invisible" test? The thread struggled with this question.

One commenter offered a framework: "All tools I've used are either simple and heavily limited (so, not 'invisible' because hard things are hard) or powerful but heavily specialized (so, not 'invisible' because the learning curve is very evident). I feel the trade off is inescapable."

Examples that came up as "close to invisible":

• Automatic transmission in cars
• SSH
• Google Search
• Tiling window managers (for those who've internalized them)
• Syntax highlighting
• Deterministic autocomplete

The counterargument: these tools are only invisible because you've already internalized them. To someone who's never used a tiling window manager, it's anything but invisible.

The Practical Takeaway

The essay's core challenge is worth sitting with: are you actually more productive with your current toolchain, or do you just feel more productive?

Bill's test is simple: wall-clock time and accuracy. If you're spending 10 minutes crafting a clever macro for something that would take 2 minutes with multiple cursors or a script, the macro isn't serving you - it's serving your desire to feel clever.

This doesn't mean you should abandon Vim or Emacs. It means you should be honest about whether your tool investments are paying dividends in output, not just in the satisfaction of mastery.

Sources

• Good Tools Are Invisible - Ginger Bill
• Hacker News Discussion
• Odin Programming Language