Attached: 1 image
Hey folks!
Did you hear the news? Vanilla OS 2 Orchid Developer Previews are now available for download 🚀
Let us know what you think :)
Please note that these builds are unstable and are not recommended for daily use.
https://vanillaos.org/blog/article/2023-07-05/vanilla-os-orchid---developer-preview
#Linux #FLOSS #OpenSource
Due to legal reasons, Fedora is not able to distribute their distro with everything baked in to ensure (close to) maximum functionality out of the box. Notoriously, codecs required for (some of the) hardware acceleration and enabling the use of some multimedia file types are not delivered out of the box. Therefore, users are required to set those up themselves. Thankfully, RPM Fusion steps in to the rescue and makes it a lot easier for the end user to acquire these nonetheless.
But…, what if retroactively Fedora is forced to remove even more stuff and what if the solution is not directly available on RPM Fusion and thus requires (advanced) manual intervention in order to resolve the problem for the end user? Which actually happened just a few months ago with the mesa drivers*. Or what if a new Nvidia update causes troubles and you can’t boot into your system? Which actually happens once every often if you don’t pay attention and/or are unlucky. These are real problems that require real solutions; solutions which Fedora can’t offer in the most elegant way in fear of the court (rightfully so).
This is where the “batteries included”" expression comes in. The aforementioned two problems were nonexistent on images provided by uBlue. Because problematic images are hold back by default automatically, which cautions them to resolve it ASAP and within a day (so far) the workaround gets built-in to the image and the end-user just gets the solution without ever noticing that something was wrong in the first place. Why? Because the end user’s system never got the update without the workaround in the first place. An interaction unique as such within the Linux space is simply unheard of. I’m only aware of Vanillas OS that might be able to pull off something similar in the near future. Which is why I’m also very excited to see how it develops.
Furthermore, as the end user you never had to go to the RPM fusion page in the first place to get/set up the earlier mentioned codecs as they were actually built-in to the image by default. That, is also part of the “batteries included” expression.
If you’re interested, please consider checking out their documentation. Furthermore, please feel to inquire, if you so desire 😉 !
Alright, got it. Thanks for the explanation! I’m actually running ublue on two computers right now (bazzite on my desktop, beyond on my laptop, although I’m rebasing soon), so I’m not like a total noob to all this, and I have read the docs. I was just having trouble parsing an idiom.
Due to legal reasons, Fedora is not able to distribute their distro with everything baked in to ensure (close to) maximum functionality out of the box. Notoriously, codecs required for (some of the) hardware acceleration and enabling the use of some multimedia file types are not delivered out of the box. Therefore, users are required to set those up themselves. Thankfully, RPM Fusion steps in to the rescue and makes it a lot easier for the end user to acquire these nonetheless.
But…, what if retroactively Fedora is forced to remove even more stuff and what if the solution is not directly available on RPM Fusion and thus requires (advanced) manual intervention in order to resolve the problem for the end user? Which actually happened just a few months ago with the mesa drivers*. Or what if a new Nvidia update causes troubles and you can’t boot into your system? Which actually happens once every often if you don’t pay attention and/or are unlucky. These are real problems that require real solutions; solutions which Fedora can’t offer in the most elegant way in fear of the court (rightfully so).
This is where the “batteries included”" expression comes in. The aforementioned two problems were nonexistent on images provided by uBlue. Because problematic images are hold back by default automatically, which cautions them to resolve it ASAP and within a day (so far) the workaround gets built-in to the image and the end-user just gets the solution without ever noticing that something was wrong in the first place. Why? Because the end user’s system never got the update without the workaround in the first place. An interaction unique as such within the Linux space is simply unheard of. I’m only aware of Vanillas OS that might be able to pull off something similar in the near future. Which is why I’m also very excited to see how it develops. Furthermore, as the end user you never had to go to the RPM fusion page in the first place to get/set up the earlier mentioned codecs as they were actually built-in to the image by default. That, is also part of the “batteries included” expression.
If you’re interested, please consider checking out their documentation. Furthermore, please feel to inquire, if you so desire 😉 !
Alright, got it. Thanks for the explanation! I’m actually running ublue on two computers right now (bazzite on my desktop, beyond on my laptop, although I’m rebasing soon), so I’m not like a total noob to all this, and I have read the docs. I was just having trouble parsing an idiom.