This, among many other reasons, is why I still use Terminal.app. I switched to iTerm for true color, but when Tahoe added it to Terminal.app- I switched back.
Without all thw unnecessary headings, "color", and constant "Let. That. Sink. In."-esque recaps this would be 2 paragraphs. Just let it be! Readers don't need the slop.
Yeah that was my first thought. Use a TUI that abuses the terminal to make a experience poorly recreating an actual GUI, don't be shocked if it doesn't turn out very efficient
Yeah, welcome to 1980, where a library coming from a roguelike shaped almost all the TUI's for Unix until ~2010 or so, Curses.
A 386 could run NetHack at blazing fast speeds and read the news in a TTY perfectly well.
A multicore machine can't get the basic thanks to the 'wonderful' JS. Heck, even s9 Scheme from http://t3x.org ships a Curses module, enough to drive some text and maybe boxes/menues and it should fit in two floppies. A single one if the image it's generated later on-disk.
Good tools will have an option to disable the spinner. Haven't used Claude Code yet so don't know if it falls into the category of "good tools" by that definition. :-)
I like what you need to know a bazillion ways to disable all this unnecessary cruft.
And people would be angry if you even note what you don't need it.
I propose we should have some global switch to on/off these type of things, something like kern.fidget.widget=off or $VANILLA_PUMPKIN_LATTE=BROYEETSURE
I won't use neither Claude, nor a MacBook; I would just keep chilling out programming
with decent tools and a bare XTerm to accomplish the rest. I can get Aragonese bricks ^U sweets in the meanwhile.
On Terminal.app, I wonder if the GNUStep eversion and the ones bundled with Mac OSX shared some code.
I don’t use MacOS or Claude Code, but I do use Kitty terminal on Linux, which the author suggests has the same issues that plague him using Ghostty.
Kitty is a magnificent piece of software that has radically enhanced the interface between me and my computer. And it does this while consuming negligible resources.
I don't know that I have ever understood a reason to leave the native terminal included with any given OS, particularly after the Windows modernization pass in recent years on the terminal.
Same. Need multiple terminals visible at once? New window. Need a few separate sessions? New tab(s).
All the bells and whistles people have shown me over the years... it never even gets close to making me think "oh yea, that's better than basic tab/window management and the terminal app that comes with my OS".
tiling managers like Terminator are, to me, the most efficient. Something like Blender for hybrid customization might be a sweetspot. Blender allows for arbitrary layout and essentially tab control in any tile.
layout, multiplexing, tab-complete, history, using the same interface across multiple systems, ligatures...
There are lots of distributions that ship emulators that don't have modern features, and even among those that do, I still don't want to learn the individual quirks every time I hit a shell.
Gnome terminal, yakuake, ptyxis, cosmic, konsole, xfce4-terminal, qterminal, etc all have slight variations between simple things like rendering and more important things like hotkeys. It's nice to have an alternative that I can install on any system such that I can get comfortable with just the one. If I can't install anything I'm often stuck poking around to find whatever the devs version of correct is, or else asking the owner of the machine "okay, how the hell do I do {x}?" if they're comfy with their cli, but chances are if I'm sitting there it's because they're not comfy with their cli.
I could cover a lot of it with a bashrc file, but I wouldn't want anyone fucking with mine, so I'm not touching anyone elses.
My terminal is not burning battery anywhere at all like mining bitcoin, and neither is yours.
If you're not benefitting from the ability to offload your terminal rendering to GPU, why are you using a terminal that offloads terminal rendering to GPU in the first place?
Imagine running something massively CPU bound, but you've still got to spin up perhaps tens of terminals in order to simultaneously ssh in to multiple servers because you don't want to set up a remote monitoring solution because you don't want each of the servers to be running a docker image where SSH>htop would suffice.
There are plenty of situations in which one might want a terminal emulator offloaded to gpu. That you are not in any of those situations is no reason to write a hit piece throwing shade as if the packages mentioned are somehow bloated or inefficient.
Imagine whining about how you've got to pay adobe and use several gigabytes of ram to resize jpgs. You'd obviously be outside Photoshop's ideal customer profile, just as you are outside ghostty et al's.
This, among many other reasons, is why I still use Terminal.app. I switched to iTerm for true color, but when Tahoe added it to Terminal.app- I switched back.
Without all thw unnecessary headings, "color", and constant "Let. That. Sink. In."-esque recaps this would be 2 paragraphs. Just let it be! Readers don't need the slop.
I hate hate hate the style of writing LLMs make.
The issue isn't the terminal. The issue seems to be that Claude is using React to render to that terminal at 60FPS like a goddamn video game
Vibe coding is soooo awesome!
And people thought that Electron was a resource pig. You ain't seen nothing yet.
Vibe coding is unleashing man-made horrors beyond human comprehension on the world.
Yeah that was my first thought. Use a TUI that abuses the terminal to make a experience poorly recreating an actual GUI, don't be shocked if it doesn't turn out very efficient
Yeah, welcome to 1980, where a library coming from a roguelike shaped almost all the TUI's for Unix until ~2010 or so, Curses.
A 386 could run NetHack at blazing fast speeds and read the news in a TTY perfectly well.
A multicore machine can't get the basic thanks to the 'wonderful' JS. Heck, even s9 Scheme from http://t3x.org ships a Curses module, enough to drive some text and maybe boxes/menues and it should fit in two floppies. A single one if the image it's generated later on-disk.
Consider how bloated data centers are when local models are now equally capable of human-scoped problem solving.
Software bloat fills a void created by itself.
All the stupid spinners at the prompt are obnoxious. Unfortunately it’s so trendy it’s impossible to reverse course
Good tools will have an option to disable the spinner. Haven't used Claude Code yet so don't know if it falls into the category of "good tools" by that definition. :-)
I like what you need to know a bazillion ways to disable all this unnecessary cruft.
And people would be angry if you even note what you don't need it.
I propose we should have some global switch to on/off these type of things, something like kern.fidget.widget=off or $VANILLA_PUMPKIN_LATTE=BROYEETSURE
>Zaragoza, Hotel Pilar Plaza café.
I won't use neither Claude, nor a MacBook; I would just keep chilling out programming with decent tools and a bare XTerm to accomplish the rest. I can get Aragonese bricks ^U sweets in the meanwhile.
On Terminal.app, I wonder if the GNUStep eversion and the ones bundled with Mac OSX shared some code.
I don’t use MacOS or Claude Code, but I do use Kitty terminal on Linux, which the author suggests has the same issues that plague him using Ghostty.
Kitty is a magnificent piece of software that has radically enhanced the interface between me and my computer. And it does this while consuming negligible resources.
What does it do for you that, say, konsole, gnome-terminal or even xterm wouldn't?
I don't know that I have ever understood a reason to leave the native terminal included with any given OS, particularly after the Windows modernization pass in recent years on the terminal.
Splits. And tabs. But mostly splits. Nothing tmux and/or a decent window mangers wouldn't fix. But Macos.
Same. Need multiple terminals visible at once? New window. Need a few separate sessions? New tab(s).
All the bells and whistles people have shown me over the years... it never even gets close to making me think "oh yea, that's better than basic tab/window management and the terminal app that comes with my OS".
That requires a good window manager, which macOS does not have.
For the few times a month I need to have two windows/panes visible at the same time, I take five seconds positioning and sizing them then move on.
tiling managers like Terminator are, to me, the most efficient. Something like Blender for hybrid customization might be a sweetspot. Blender allows for arbitrary layout and essentially tab control in any tile.
<nerd snipe>
layout, multiplexing, tab-complete, history, using the same interface across multiple systems, ligatures...
There are lots of distributions that ship emulators that don't have modern features, and even among those that do, I still don't want to learn the individual quirks every time I hit a shell.
Gnome terminal, yakuake, ptyxis, cosmic, konsole, xfce4-terminal, qterminal, etc all have slight variations between simple things like rendering and more important things like hotkeys. It's nice to have an alternative that I can install on any system such that I can get comfortable with just the one. If I can't install anything I'm often stuck poking around to find whatever the devs version of correct is, or else asking the owner of the machine "okay, how the hell do I do {x}?" if they're comfy with their cli, but chances are if I'm sitting there it's because they're not comfy with their cli.
I could cover a lot of it with a bashrc file, but I wouldn't want anyone fucking with mine, so I'm not touching anyone elses.
edit: distrObutions->distrIbutions
iTerm2 has builtin native tmux integration
Game changer
My terminal is not burning battery anywhere at all like mining bitcoin, and neither is yours.
If you're not benefitting from the ability to offload your terminal rendering to GPU, why are you using a terminal that offloads terminal rendering to GPU in the first place?
Imagine running something massively CPU bound, but you've still got to spin up perhaps tens of terminals in order to simultaneously ssh in to multiple servers because you don't want to set up a remote monitoring solution because you don't want each of the servers to be running a docker image where SSH>htop would suffice.
There are plenty of situations in which one might want a terminal emulator offloaded to gpu. That you are not in any of those situations is no reason to write a hit piece throwing shade as if the packages mentioned are somehow bloated or inefficient.
Imagine whining about how you've got to pay adobe and use several gigabytes of ram to resize jpgs. You'd obviously be outside Photoshop's ideal customer profile, just as you are outside ghostty et al's.