91–98 of 98 posts
Speaking of slow, what I absolutely cannot comprehend is why ghostty is so popular. Despite being written in Zig it is very slow and a total CPU and memory hog. Just sitting there idle it’s pulling a constant 40% of my CPU? No thanks!
This. Ghostty is significantly slower than Kitty on my Arch setup. It's still fast enough I guess, but no reason to switch from Kitty for me.
Earlier quoted context omitted.
This. Ghostty is significantly slower than Kitty on my Arch setup. It's still fast enough I guess, but no reason to switch from Kitty for me.
Software accel?
I'm surprised people are still using nvm, considering it's impact on shell startup time. I can't recommend switching to mise highly enough: https://mise.en.dev/
How often do you launch a fresh terminal though? I start mine with a script to have favourite tabs ready at boot and then generally not much afterwards.
Earlier quoted context omitted.
I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds its own input latency. I use Ghostty, which is GPU-accelerated and native, and my config is just seven lines long." I do not use Ghostty or anything similar^1 1. https://en.wikipedia.org/wiki/List_of_terminal_emulators Further, the terminal emulator cited by th…
"I do not use a graphics driver" Maybe this is not clear. I apologise for any ambiguity vga(4) can be referred to as a "graphics driver" For example, https://man.netbsd.org/vga.4 But it does not support (non-text) graphics It only supports text The blog author is using a graphics layer such as X11 or Wayland along with a terminal emulator such as Ghostty on top of it I do not use those things
"The single biggest win is what's not there: no oh-my-zsh, no prezto or plugin manager. I've honestly never understood the appeal of these frameworks." "Most of these optimizations are about leaving stuff out. It's about being intentional and only adding things you're going to use." I don't use X11 or a similar graphics layer, only textmode. Thus I don't use a terminal emulator I don't use zsh. I use NetBSD sh Smalle…
I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds its own input latency. I use Ghostty, which is GPU-accelerated and native, and my config is just seven lines long." I do not use Ghostty or anything similar^1 1. https://en.wikipedia.org/wiki/List_of_terminal_emulators Further, the terminal emulator cited by th…
"VGA graphics driver"
"This driver handles VGA graphics..."
I only use VGA textmode
I do not context switch into a graphics mode via 13h. No need
The blog author mentions that his terminal emulator is "GPU-accelerated" ("GPU" stands for "Graphic Processing Unit")
I don't use a terminal emulator that requires a graphics mode or one that uses a GPU
I'm interested in "text processing", displaying text. I like reading
I'm not interested in displaying images
"The single biggest win is what's not there: no oh-my-zsh, no prezto or plugin manager. I've honestly never understood the appeal of these frameworks." "Most of these optimizations are about leaving stuff out. It's about being intentional and only adding things you're going to use." I don't use X11 or a similar graphics layer, only textmode. Thus I don't use a terminal emulator I don't use zsh. I use NetBSD sh Smalle…
I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds its own input latency. I use Ghostty, which is GPU-accelerated and native, and my config is just seven lines long." I do not use Ghostty or anything similar^1 1. https://en.wikipedia.org/wiki/List_of_terminal_emulators Further, the terminal emulator cited by th…
I do not use a "desktop" environment
As such, I do not need the dependencies of such terminal emulators, such as "gtk" ("GIMP ToolKit") a widget toolkit for creating GUIs ("Graphical User Interfaces")
As I am only using the command line, not a "desktop", I have no need for a GUI toolkit
"The single biggest win is what's not there: no oh-my-zsh, no prezto or plugin manager. I've honestly never understood the appeal of these frameworks." "Most of these optimizations are about leaving stuff out. It's about being intentional and only adding things you're going to use." I don't use X11 or a similar graphics layer, only textmode. Thus I don't use a terminal emulator I don't use zsh. I use NetBSD sh Smalle…
I use the term "terminal emulator" in the same sense as in the blog post: "The terminal itself Shell startup is only half the story, because the emulator adds its own input latency. I use Ghostty, which is GPU-accelerated and native, and my config is just seven lines long." I do not use Ghostty or anything similar^1 1. https://en.wikipedia.org/wiki/List_of_terminal_emulators Further, the terminal emulator cited by th…
The blog author is using more than the VGA driver to display text, as indicated by the reference to "GPU-accelerated"
1. Some call this a "graphics driver" while others state it "does not do graphics"
2. For example, drivers with names ending in "fb", such as "vesafb"
"The single biggest win is what's not there: no oh-my-zsh, no prezto or plugin manager. I've honestly never understood the appeal of these frameworks." "Most of these optimizations are about leaving stuff out. It's about being intentional and only adding things you're going to use." I don't use X11 or a similar graphics layer, only textmode. Thus I don't use a terminal emulator I don't use zsh. I use NetBSD sh Smalle…
The author of the blog post is using both (a) terminal emulator userland software and (b) kernel module(s) that perform terminal emulation
I only use one. I do not use a userland terminal emulator program