Closed CarterLi closed 12 months ago
I don't use the LGBT+ flag colors, though they don't look ugly for me at all. Some arts (like Fedora's) look even better with LGBT+ flag colors.
I use this repo for neofetch and appreciate all the newly added distros. I don't mind the flag colors but maybe consider separate colors for the background and logo. Example flag color background and white logo
I use this repo for neofetch and appreciate all the newly added distros. I don't mind the flag colors but maybe consider separate colors for the background and logo. Example flag color background and white logo
Automatically separating background and foreground already exists in HyFetch for a while now:
IMHO they all seems worse with LGBTQ-flag colors enabled because LGBTQ-flag colors are not content aware. The only exception is macOS, which seems no much difference.
The core idea behind HyFetch coloring isn't just to make logos look nicer, it's about representation and identity. While it's okay to assess the visual appeal, you also need to understand that the LGBTQ+ flag colors serves a much deeper purpose than just aesthetics.
For many in the LGBTQ+ community, these flags symbolize their identity, struggles, and pride. Integrating these symbols into a showcase of the tech specs they share can provide a sense of empowerment. It's combining their enthusiasm for their favorite distro / hardwares with their LGBTQ+ identity.
Also, by including flag coloring along with the updated neofetch, we're also broadcasting a wider message about the importance of inclusivity and representation. It's not just a design choice, it's a statement that promotes awareness and understanding toward the LGBTQ+ community.
I'm out of ideas improving fastfetch, and considering LGBTQ+ flags natively in it.
Sure, go ahead! Fastfetch is mostly your project after all, and you have the freedom to improve it as you see fit. Implementing this shouldn't take too much effort given your expertise. However, please approach it with sensitivity and respect for the community.
...so that we get better performance and MUCH better Windows compatibility
Windows compatibility is something I've been working on over the past releases, it'll get better as we develop more and more workarounds. But you're right that python + bash will never be as fast as something native.
Sorry to comment on a closed issue. I suggest we put this paragraph in the FAQ in README.md
(with some changes of course)
The core idea behind HyFetch coloring isn't just to make logos look nicer, it's about representation and identity. While it's okay to assess the visual appeal, you also need to understand that the LGBTQ+ flag colors serves a much deeper purpose than just aesthetics.
For many in the LGBTQ+ community, these flags symbolize their identity, struggles, and pride. Integrating these symbols into a showcase of the tech specs they share can provide a sense of empowerment. It's combining their enthusiasm for their favorite distro / hardwares with their LGBTQ+ identity.
Also, by including flag coloring along with the updated neofetch, we're also broadcasting a wider message about the importance of inclusivity and representation. It's not just a design choice, it's a statement that promotes awareness and understanding toward the LGBTQ+ community.
EDIT: You know what, let me make a pull request :)
Hello all,
I'm out of ideas improving fastfetch, and considering LGBTQ+ flags natively in it, so that we get better performance and MUCH better Windows compatibility.
Before doing that, I want to know that if it's worth the effort. Here are some comparisons between LGBTQ colors enabled logo and original ones.
IMHO they all seems worse with LGBTQ-flag colors enabled because LGBTQ-flag colors are not content aware. The only exception is macOS, which seems no much difference.
What's your opinion? Did you get into this repo for upgraded neofetch only, or were really using hyfetch?
Disclaimer: This should be in discussion. However discussion in this repo is not open. So I put it here.