-
It's not like Goyal doesn't accept any patches [1].
I don't use kitty myself, but many people who do seem to love it. I've come around to feel that this is truly a maintainer's judgment call. After all, they are almost always stuck maintaining the code no matter who wrote it initially, and they know better than anyone else what code they're personally comfortable maintaining.
More generally, if you like a piece of software enough, you're implicitly trusting the maintainers' judgment. You're certainly not reviewing every single line of code they write to see if you agree with it.
The miserable survival rate of hostile forks also demonstrates that even if people care enough to fork over one issue, they rarely care enough to maintain the overall project long-term, despite implicitly asking the original maintainers to do the exact same thing.
[1] https://github.com/kovidgoyal/kitty/graphs/contributors
-
InfluxDB
Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.
-
repo: https://github.com/gpakosz/.tmux.git
-
https://github.com/tmux-plugins/list
As a neovim user I can also very much recommend this vim plugin to seamlessly navigate between tmux panes and neovim windows:
-
there are hacky ways to do it though:
http://github.com/nelhage/reptyr
http://github.com/jerome-pouiller/reredirect
https://github.com/lkundrak/retty/
-
libsixel
A C language SIXEL encoder/decoder implementation, forked from saitoha/libsixel after @saitoha vanished. Receives security patches, accepts PR's filed preferably here but also at saitoha/libsixel. (by libsixel)
They did take over maintenance but abandoned it shortly after: https://github.com/libsixel/libsixel/
You can add this to the enormous pile of open source forks that didn't survive long enough to have any real value to the industry.
I respect that Goyal has been bitten by this dynamic before and said this back in April 2020:
> That said, I wont refuse a patch to implement it on top of the existing graphics support, provided I was reasonabl confident the person implementing it would stick around to maintain it as well.