71–80 of 168 posts
Geeking out on terminals is like geeking out on shoelaces. I'm glad you guys are out there - someone has to do it.
I once took around two weeks worth of evenings to get my zsh startup from 300ms down to 50ms because it felt laggy. Fuck nvm btw.
It matters!
There is some number of fps where "the human eye can't tell the difference" I bet there is one for ms delays
Gutenberg's copy of Moby Dick is 1.2MB[0]. Which is to say the slowest benchmarked terminal could display a paltry ~53 Moby Dicks per second, while shitty gives you ~98 Moby Dicks. I am not sure how many Moby Dicks I require per second, but it is good to have options. [0] https://www.gutenberg.org/ebooks/2701
Earlier quoted context omitted.
I guess I just didn't notice. In any case, it wouldn't have been std::thread, but https://github.com/pg83/std/blob/master/std/thr/thread.h from my bike lib!
What do you mean you didn't notice? I saw another comment about Claude below, are you not even reviewing the output? I just browsed the project for two minutes and it's one of the first things I noticed. std::thread is more portable (Windows, if anyone cares) and allows you to pass in a lambda, which keeps the code local and also has the compiler generate the closure for you instead of having to pass function pointer…
Of course I looked at the LLM output, but people, uh, make mistakes and can miss something.
> std::thread is more portable (Windows, if anyone cares) and allows you to pass in a lambda, which keeps the code local and also has the compiler generate the closure for you instead of having to pass function pointers and void* captures around. I don't see any advantage to using pthread directly.
These are obvious things, and the objections to them are equally obvious. For example, std::thread is an additional level of abstraction over pthreads, which, in essence (not in form), gives me nothing. And I don't care about Windows, really.
I will def try this out and I absolutely love the name. Just an A++ name
Like a neighborhood kid outside on his bike yelling “shit” then pedaling away as fast as he can, to dissociate himself from the event out of fear of getting caught.
FaTTY - Fast Terminal (executable named “ft”)
RaTTY - Rapid Terminal (“rt”)
LighTTY - Lightspeed Terminal (“lt”)
Dragster (“dt”)
McQueen (“mt”)
Names are hard, but it’s trivial to come up with a name better than “shitty”.
Going by the childish naming of the project, it doesn't inspire confidence in the professionalism of the author going forward, and neither will it help with getting it installed on corporate networks. I'm all for vulgar wit but this isn't that (yes I'm aware of the -tty convention) & just reinforces the cliche of tech skills inversely proportional to social ones
I assure you, this is a very professionally made product: - we have 5,000 tests covering all aspects of terminal behavior - we have address sanitizer and ub sanitizer runs of these tests - we also have regular fuzzing! - we even monitor code coverage This is definitely a top 0.1% GitHub project in terms of development approach. > and neither will it help with getting it installed on corporate networks. I'm fine with…
Earlier quoted context omitted.
I assure you, this is a very professionally made product: - we have 5,000 tests covering all aspects of terminal behavior - we have address sanitizer and ub sanitizer runs of these tests - we also have regular fuzzing! - we even monitor code coverage This is definitely a top 0.1% GitHub project in terms of development approach. > and neither will it help with getting it installed on corporate networks. I'm fine with…
[flagged]
It's quite obvious to me that professionalism in product manufacturing correlates very weakly with naming :) Proof me wrong.
Nice work! I do wonder, however, whether people really have issues with perf on any terminal emulator in 2026 I’ve been living in Terminal.app / zsh / tmux / vim for 15 years and have never once thought “this is slower than I want.”
To me, the most relevant aspect is the time it takes to open. I can't believe how slow the startup time in common linux distributions is by default, it's so annoying, by the time it opens I already forgot what I wanted to do. Alacritty has this cool feature where you only ever have to "open" a single terminal, whereas new windows can be created very efficiently with `alacritty msg create-window`, being forks of the i…
Gutenberg's copy of Moby Dick is 1.2MB[0]. Which is to say the slowest benchmarked terminal could display a paltry ~53 Moby Dicks per second, while shitty gives you ~98 Moby Dicks. I am not sure how many Moby Dicks I require per second, but it is good to have options. [0] https://www.gutenberg.org/ebooks/2701
Besides, most screen only show 60 images per second. That's not many Moby Dicks per second.
Earlier quoted context omitted.
Why did you make this comment? It's completely off topic. Your appeals to authority do not apply when the author is clearly telling you not to use it for that. We're well past the point where this kind of software eventually ends up under corporate use policy or any policy at all.
The name screams for attention, so of course it's on topic. I made no appeal to authority, just maturity.