So I was interested to dig more into this..., but I wasn't able to find any other source that talked about this. Furthermore, while some digging suggests that the author is a real person, the text didn't score well on https://undetectable.ai/ . Do with that whatever you will*
FWIW, trying to install it within a distrobox container gave the following error:
error: target not found: rye-init
Which, AFAIK, suggests that the package is not found in the repo. Nor does going through https://archlinux.org/packages/ yield any results. At this point, my best best would be to spin up a VM and see if that makes a difference. But I'm not really in the mood at the moment.
Regardless, has somebody checked the package out for themselves? Or, have they seen discussions on it elsewhere?
While Red Hat does a lot to enable Fedora (and the Linux ecosystem in general), Fedora remains a community distro. It just happens to receive significant backing. Which, one might argue, isn't a lot different to how SuSE backs openSUSE. Heck, while (arguably) in a different order of magnitude, Canonical contributes to Debian and even Valve contributes to Arch.
But, to underline an important aspect to the RedHat-Fedora relationship, Fedora does not have to follow Red Hat in everything. Like how Fedora continues to default to Btrfs as its filesystem while Red Hat has deprecated Btrfs for 7 years now.
Yet, I don't want to underscore that both Arch and Debian can probably easily keep the lights on if any contributing party would cease its support. On the other hand, if Red Hat or SuSe would stop contributing to Fedora or openSUSE respectively, then it would at least require a huge restructuring for them to have a chance at surviving the aftermath. So, in that sense, both Fedora and openSUSE are dependent on their respective big backers.
As for concerns related to Red Hat, they did like two bad things (I think) that go against the spirit of open source sortware. But these pale to their contributions. With PipeWire, systemd and Wayland; they've literally built the backbone of modern Linux. Boycotting them will likely result in picking some niche Linux that might be a huge pita to operate.
If you're interested in a deep dive, then consider looking into this thread and the links found within.
The following gif demonstrates folding:
The following gif demonstrates folding:
The following gif demonstrates folding:
While I don't enjoy the fact that this introduces a ton of maintenance issues on systemd-less systems that would like to continue supporting GNOME, I do think leveraging systemd to elegantly revive the session save/restore functionality bodes a lot of optimism for the set of features that will follow.
I'm at least thankful that this maintainer/contributor dedicated about half of their announcement on how systemd-less systems could alleviate this issue.
And if GNOME is considered “not very customisable” in the linux world, KDE, Cinnamon, etc. must be even more customisable
It's more like GNOME doesn't come with a lot of customization options OOTB. You need extra tools -be it Tweaks, Extension Manager or the somewhat archaic Dconf Editor- to unleash the plethora of customization options in a palpable manner.
On the upside, GNOME's extensions do allow for extensive customization with 'ease'. Heck, this often goes beyond what other DEs are capable of (see e.g. PaperWM^[Which has inspired a full-blown WM in Niri.] or Material Shell^[For which Nicco, a KDE developer that also makes content on YouTube, said that its customization (likely) goes beyond what was possible on KDE Plasma at the time.]).
Included is the following disclaimer by the author:
- This may not be representative of all types of Linux users. I’m sure this is not what your AWS engineer uses on EC2.
- This may not be completely representative of all Linux gamers either. But I’d wage this is actually a good predictor where the market is going to shift. We saw first that Manjaro was getting the boot here first, before going under pretty much everywhere.
- There may be some additional biases, due to whoever used ProtonDB.
- Flatpak is NOT a distro, but that’s what Steam reports when it’s running on Flatpak, and Flatpak being distro independent we report it as a separate environment, if that makes sense. Feel free to ignore it if you wish.
- Arch Linux is Arch Linux on desktop. The Steam Deck’s OS is reported as HoloISO, not Arch Linux, so stop trying to claim that Arch is first because of the Steam Deck! This is mainly data reported from desktop PCs, so no, SteamOS is not a thing at the moment on such machines. This may change as Valve starts providing official support beyond the Steam Deck.
Included is the following disclaimer by the author:
- This may not be representative of all types of Linux users. I’m sure this is not what your AWS engineer uses on EC2.
- This may not be completely representative of all Linux gamers either. But I’d wage this is actually a good predictor where the market is going to shift. We saw first that Manjaro was getting the boot here first, before going under pretty much everywhere.
- There may be some additional biases, due to whoever used ProtonDB.
- Flatpak is NOT a distro, but that’s what Steam reports when it’s running on Flatpak, and Flatpak being distro independent we report it as a separate environment, if that makes sense. Feel free to ignore it if you wish.
- Arch Linux is Arch Linux on desktop. The Steam Deck’s OS is reported as HoloISO, not Arch Linux, so stop trying to claim that Arch is first because of the Steam Deck! This is mainly data reported from desktop PCs, so no, SteamOS is not a thing at the moment on such machines. This may change as Valve starts providing official support beyond the Steam Deck.
I was trying to stir a discussion/conversation: How much can we tolerate from our beloved (F(L))OSS developers? Can they get away with anything as long as they return with some promise?f
The fact remains though: why did they literally go radio silence on this issue for over a year? Like, a simple, "I would like to notify everyone that I'm working on this." would have been sufficient. Was that too much to ask?
The guy is trying to address the issue and he is building this in his free time. Give him some credit at least, I am sure this is consuming a lot of his free time.
Fam, you've chosen to trust them for reasons that are unclear to me. Honestly, I don't see anything (yet) that would clear their name. For all we know, they could have ties to some intelligence agency; which the infamous Jia Tan has (retroactively) been accused of as well.
I personally find this Ventoy an amazing piece of software
That's not the issue. I've also made plenty use of it in the past. But at what point do you start to second guess the intent behind the maintainer?
he also seems to be willing to address the issue and be more transparent in the future which is also commendable.
Again, arguably too little too late. They literally ghosted the issue for over a year. Then, within 24 hours of possible proof of malicious code, they appear and (perhaps) "pose the image" of putting in a gargantuan effort to resolve the issue. But, like, where were they for a year? Furthermore, the hints of justifications for their actions are simply not up too par.
Don't get me wrong. As I clearly hinted at it in my previous comment, if they pull through and provide/produce (bit-by-bit) reproducible builds of Ventoy^[Another spoiler-alert: They admitted that it would be hard. Which is fine, but could be interpreted as the first action for an eventual cop out. Only time will tell...], then I obviously have no qualms against them or their software. Why would I? But until then, I will steer clear.
What should have happened for you to be more concerned?
Perhaps I'm too skeptical and/or have trust issues, but isn't this too little too late? This issue had been ignored for so long, but -suddenly- within 24 hours of this very peculiar find^[Spoiler alert: Ventoy's sister software -called iVentoy- employs a trick that has been utilized for installing compromised kernel drivers.], Ventoys maintainer goes into full damage-control mode. Should we just accept that?
Sorry, at least for now, I simply don't buy it.
As someone with a perpetual desire for clean system management—even back in my M$ days^[Which I 'dealt' with by factory resetting every few months 😅]—I deeply resonate with the desire to declare the desired state within a config file and treating it as the single source of truth; this is exactly why NixOS with the Impermanence module has captivated me ever since it appeared on my path, like a long-sought truth.
I've only abstained this long due to lacking a spare device for a proper test run that might lead to permanent adoption. Perhaps this summer will finally be the time to take the plunge.
Looking forward to bringing order to chaos at last.
Why? The likes of Alpine Linux and Chimera Linux don't adhere to GNU/Linux to begin with. Even Ubuntu has intentions to replace the GNU coreutils with alternatives that have been written in Rust.
Don't get me wrong; GNU has been instrumental for enabling the Linux ecosystem to begin with and will probs remain relevant (at least to some capacity) for the foreseeable future. However, I absolutely don't see any reason to be pedantic about this; especially as something like systemd -whether you like it or not- has become a lot more important for what mainstream Linux has become. Yet, nobody in their right minds would even consider to refer to Linux as systemd/Linux (thankfully so).
To add to this, a 'distro' -if you will- that was launched recently with this theme would be the aptly-named Blue95.
Yeah lol. There are definitely some oddities going on that I find hard to wrap my head around.
For example, last week this article was published on the same website and attributed to the same author. In the article, the author talks about the release of Fedora 41. The thing is, however, that Fedora 41 was released last October. Heck, Fedora 42 has been released for two months now. Like, why wouldn't they want to talk about Fedora 42 instead?