You know the feeling. You download a new terminal, lured in by a slick website and a gradient logo, only to find it hogs 2GB of RAM just to render a blinking cursor. The software industry has become obsessed with polish, mistaking aesthetics for actual performance. Enter “shitty”—a memory-unsafe terminal that just dropped on Hacker News and is making a mockery of the entire ecosystem.
In a world obsessed with making everything look like a glassy, animated Apple keynote, the only true rebellion left is calling your software “shitty”.
At first glance, you think it’s a joke. The desktop application and icon are literally named “shitty.” But look at the performance numbers. It’s unapologetically fast. It rivals established heavyweights like Alacritty and Ghostty. The creator is simultaneously mocking the terminal ecosystem and outshining it.
Most people will look at the name, roll their eyes, and move on. They want polish. They want a friendly onboarding tutorial. But that’s exactly the point. The best filter against entitled users isn’t a paywall—it’s an offensive name. By deliberately choosing a self-deprecating, almost insulting label, the creator instantly repels anyone who needs their hand held. What’s left behind is a high-signal, low-noise community of developers who just want raw speed.
The Hacker News comments tell the whole story. One user noted, “Unironically better name than ‘CRM’ for a CRM.” Another simply asked, “Why wouldn’t you use this?” It’s a refreshing counter-example to the bloated, over-marketed tools we suffer through daily. It raises a real question: are our polite, corporate naming conventions actually holding back honest engineering?
When the branding is zero, the engineering has to be everything. The “shitty” terminal proves that branding can be perfectly inversely correlated with technical quality. It doesn’t need a mascot. It doesn’t need a mission statement. It just needs to be faster than yours.
FAQ
Q: Isn't this just a gimmick that sacrifices usability for a cheap laugh?
A: No. The performance benchmarks are dead serious, rivaling established terminals like Alacritty and Ghostty. The name is a joke, but the engineering is not.
Q: Should I name my next open-source project something vulgar?
A: Only if you want to intentionally filter your user base. A provocative name acts as a moat against entitled, high-maintenance users, leaving you with a community that actually cares about the code.
Q: Is polite software engineering actually holding back performance?
A: Often, yes. The obsession with safe, marketable, and 'polite' branding usually comes with a layer of abstraction and bloat. Stripping away the branding forces a pure focus on technical execution.