3 ms·
I use Alacritty exclusively, and knowing that the maintainer is discerning makes me like it even more. I'm getting what I signed up for, which is a project whic
by thenoblesunfish 5y ago
I use Alacritty exclusively, and knowing that the maintainer is discerning makes me like it even more. I'm getting what I signed up for, which is a project which cares deeply about doing a few things very well. I think that an unstated implication of that ethos is that there will be plenty of things that you would like to do, but upon some amount of investigation don't see how to do well enough, so you don't do them and move on to devote your precious time and energy to other things related to your code, which remains an enjoyable place to work. That looks like the story of that ligatures PR.
- nchudleigh 5y agoIn this camp, my tty needs are simple. Alacritty is simple- and works well. IMO core maintainers call the shots on what to accept and what not to. As others have mentioned, if you don't like it- fork and build your own.
- nixpulvis 5y agoI have the utmost respect for Chris. One thing I've learned from working with him a little bit was that there's a huge importance to both the medium and the timing of the message. Balancing even just IRC and GitHub PR comments is a tough game to play, but it must be played if you want to be successful. Treating PRs like IRC will get you in trouble, while reading IRC like a PR might leave you in the dust. Knowing when to move an argument from IRC to a longer form like a PR or Issue is a critical skill (one I never was very good at). Chris and team, if you happen to read this. Thanks again for all that you do.
- jwcooper 5y agoI agree with this as well. I use Alacritty all day, every day for work. It does exactly what I need and is very fast and stable.