|
|
|
|
|
|
by intertextuality
2603 days ago
|
|
|
You say the small things. You mean like, how quickly the terminal opens and how quickly text gets painted on the screen? iTerm2 blows hyper out of the water in those regards, and it actually does add up. Styling otherwise really isn't that difficult, but it begs the question of why do you need so much information? Are you actually developing or just spending time tinkering on your terminal to have bells and whistles that you don't actually even look at? Surely a simple colorscheme + font that aliases correctly should be enough to "feel nice" to look at? The only thing keeping me from the better performance of alacritty is iterm2's infinite scrollback and some other miscellaneous features that alacritty will probably never get. |
|
|
It's less about having lots of info and more about being able to control how it's displayed. I really only have a few things I keep around in my prompt / status bar, and they're all immediately useful to the task at hand and are reflective of the current project I'm working inside - I jump around a lot between tech stacks for personal and work environments, and being able to know where I am is important:
- what's the git status of this project
- is this a Python or Node app
- am I inside a virtualenv
- what's the Kubernetes cluster context name
- what's the currently active Kubernetes namespace
I really hate visual clutter, so the ability to move some of this stuff to a status bar rather than keeping it around on every repaint of the prompt, and be able to exactly style it as desired with CSS, is what attracted me to Hyper. This applies to the whole UI, if there's any element I don't like, I can change it.
Similar to you, I've considered switching to Alacritty, but it doesn't hit the features/customization to performance ratio for me.