You’ve probably been using the same terminal for years. We all have. We download iTerm2, or maybe we’ve recently switched to Ghostty, and we stick with it because the thought of building a better one sounds like a months-long slog of dealing with obscure APIs and rendering bugs. But what if it didn’t? What if you could build a functional, native macOS terminal with Git integration in just five days?
I did exactly that, and the result is forcing a rethink of what ‘good enough’ actually means in developer tooling. But before you rush to replace your daily driver, there’s a massive catch.
Speed is a feature, but polish is the only thing that keeps users from actually switching.
When you build something in five days, you prove a point: rapid prototyping isn’t dead, and indie developers can still disrupt spaces dominated by massive open-source projects. The Git integration works. The native macOS feel is there. It’s a minimal viable product that functions exactly as intended. But then the Hacker News crowd descended, and the top comment cut right to the bone: ‘Is there anything particularly outstanding about this compared to the Ghostty I’m using now?’
That comment highlights the exact tension of modern software development. We assume shipping a quality terminal requires months of work. This project flips that assumption on its head. The critical missing piece, however, isn’t the Git integration or the speed of execution. It’s the user experience refinements that make a terminal stick. It’s the muscle memory. It’s the milliseconds of latency.
We don’t need another terminal that does everything; we need one that does the right things flawlessly.
You can hack together features in a weekend. You can integrate Git, build out a native UI, and push to GitHub by Friday. But competing with established players like Ghostty requires a different kind of obsession. It requires sweating the details that don’t show up in a feature list. The real challenge for any indie developer isn’t proving they can build it fast—it’s proving they can make you forget your old tool.
If your tool doesn’t make me forget my old one in five minutes, it doesn’t matter if you built it in five days or five years.
Rapid iteration is brilliant. It proves viability. But viability is just the starting line. The race is won in the UX.
FAQ
Q: What makes this 5-day terminal better than Ghostty or iTerm2?
A: Honestly, right now, it isn't. It proves that a functional MVP can be built rapidly, but established tools like Ghostty have months or years of UX polish and performance optimizations that a 5-day build simply cannot match yet.
Q: How can I apply this rapid prototyping mindset to my own dev work?
A: Stop over-engineering. Strip your project down to the absolute core feature that provides value, build it as fast as possible, and ship it. The feedback you get from real users in week one is worth more than six months of isolated perfectionism.
Q: Is building a terminal in 5 days actually a good idea?
A: It's a terrible idea if you're trying to build a commercial product to dethrone incumbents on day one. But it's a brilliant exercise in proving that the barrier to entry for developer tooling is lower than we think. Speed kills complacency.