Live data from Hacker News

Use Alacritty instead of Termite

github.com

251–260 of 331 posts

Re: Use Alacritty instead of Termite

#251

Earlier quoted context omitted.

I was experimenting with it this week as well, and that exact issue was what had me uninstall it. I guess this post doesn't add much value, but I thought the (synchronicity?) Of our experiences was interesting. It's a curious hill to die on, so to speak.

I imagine they would probably say the same thing to you. You're really not willing to use an excellent piece of software because one time you saw a dev dismiss someone who didn't like the default color scheme? How is that not even more petty?

Hey, vote with your wallet. A lot of people here on HN go out of their way to avoid products from companies that they view as poisonous, this is no different really.

Re: Use Alacritty instead of Termite

#253

I was considering switching to Alacritty earlier this week, but a quick look at some github issues changed my mind. The devs come off super toxic. Take a look at this guy that got verbal abuse for pointing out the color labeled "green" looks more like banana than lime: https://github.com/alacritty/alacritty/issues/1561 Strike 2/2 was multiple devs responding to OSX issues with "switch operating systems"

clever. review project issues before investing time in using project.

Re: Use Alacritty instead of Termite

#254
I’ve tried alacritty a few times and found it not ready for daily use. My work has me on Windows and I’ve been pleasantly surprised with the newer Windows Terminal app.

Uses the GPU for rendering (iirc the basis for alacritty’s performance claims).

Re: Use Alacritty instead of Termite

#255

I was considering switching to Alacritty earlier this week, but a quick look at some github issues changed my mind. The devs come off super toxic. Take a look at this guy that got verbal abuse for pointing out the color labeled "green" looks more like banana than lime: https://github.com/alacritty/alacritty/issues/1561 Strike 2/2 was multiple devs responding to OSX issues with "switch operating systems"

To be fair, I thought the dev’s response was adequate here. Just posting on the issue section that the “colors are wrong” while comparing with uxrvt, without any explanation or self-investigation as to why this could be a problem, has ample potential to be regarded as rude to the devs (I’m using this another terminal app and have better colors, why aren’t you fixing this?) And please note that Mac OS is NOTORIOUS for…

Adequate, meaning good enough, but with room for improvement?

Re: Use Alacritty instead of Termite

#256

Earlier quoted context omitted.

For me the killer feature is truecolor support. 256 color is rather limiting, and with truecolor you can also use gui syntax highlighting color schemes. My actual shell runs in a neovim :term, with neovim running in alacritty, so I dont care about fancy terminal features other than rendering and colors.

Why inside neovim? What's the benefit?

I used to use tmux but the vim commands were incomplete, and even with vim integration plugins, the separate buffers and separate window splitting gets in the way. I wanted to just use the same pane splitting and navigate and use the terminal output the same way I use my text in vim. Neovims term was good for the purpose, supported all the term stuff I needed, and I could open straight into it unlike in vim, so I switched to neovim. I've had no issues with terminal stuff since so I've no desire to switch. I also prefer the scrollback history in nvim over built in terminal emulator scrollbacks that I've used.

Re: Use Alacritty instead of Termite

#257

I was considering switching to Alacritty earlier this week, but a quick look at some github issues changed my mind. The devs come off super toxic. Take a look at this guy that got verbal abuse for pointing out the color labeled "green" looks more like banana than lime: https://github.com/alacritty/alacritty/issues/1561 Strike 2/2 was multiple devs responding to OSX issues with "switch operating systems"

Yeah, this was my take away as well. Also, iirc their claims of Alacritty being the "fastest" are dubious at best. I used Kitty for a while instead, which is very similar. More recently I've been trying out Foot: https://codeberg.org/dnkl/foot

Dubious indeed. I gave Alacritty a really good shot, as I was super excited to have a faster terminal. But my entire experience was plagued with slowdowns -- huge latencies, cat'ing huge files was very slow. I spent tons of time trying to tune things to make it good but it just never got there.

Basically every other "simple" terminal I've found behaves better -- xterm, urxvt, konsole, even iTerm2.

I have no idea how they can claim "fastest".

Re: Use Alacritty instead of Termite

#258

I was considering switching to Alacritty earlier this week, but a quick look at some github issues changed my mind. The devs come off super toxic. Take a look at this guy that got verbal abuse for pointing out the color labeled "green" looks more like banana than lime: https://github.com/alacritty/alacritty/issues/1561 Strike 2/2 was multiple devs responding to OSX issues with "switch operating systems"

To be fair, I thought the dev’s response was adequate here. Just posting on the issue section that the “colors are wrong” while comparing with uxrvt, without any explanation or self-investigation as to why this could be a problem, has ample potential to be regarded as rude to the devs (I’m using this another terminal app and have better colors, why aren’t you fixing this?) And please note that Mac OS is NOTORIOUS for…

>To be fair, I thought the dev’s response was adequate here. Just posting on the issue section that the “colors are wrong” while comparing with uxrvt

I went and looked at the issue, and the title is not "colors are wrong" but it is "Colors don't look as they should". Interesting how everyone comes away with what they this was said. Says a lot about the dev who responded, really.

Re: Use Alacritty instead of Termite

#259
post #3

> GTK and most of the GNOME project are much of the same. Avoid them and don't make the mistake of thinking their libraries are meant for others to use. Choose your dependencies wisely. Sometimes only a crystal ball would have helped but often, a little bit of due dilligence would have prevented lots of upgrade pain down the line.

I was also disappointed by the recent removal of static linking support in GTK [1].

It worked for a long time and now was made impossible.

The reason given was "don't want to support it".

That would make sense if it was a maintenance-intensive topic, here the only thing required is to use Meson's default options. I don't really buy the argument of "preventing to use internal APIs"; no FOSS developer in their right mind will link to internal symbols anyway.

In my opinion, an application developer should be able to choose how to link their program; toolkit developers should not forbid one way if there isn't a good technical reason.

[1] https://gitlab.gnome.org/GNOME/gtk/-/issues/3774#note_109943...

Post reply on HN