Not sure if it’s still the same as it was back in my day, but KDE’s “release candidate” nomenclature was always a bit of a misnomer. You’d never see RC1 actually released as final. What it really means is that the alpha “feature refinement” beta “bug fixing” phase is over, and it’s the final testing phase for showstoppers. However, the definition of showstopper seemed always to be very wide. Thus, a lot of bugs still get reported and fixed during this phase, and RC really means “beta, but towards the end of the pipeline”.
Which is in contrast to the Linux kernel where a RC can be declared ship-ready and simply get renamed.
Admittedly there’s a fairly large impact difference between kernel level bugs, and say a bug in Okular…
The nomenclature is actually correct here, and a lot of other software use it, at least from everything I’ve seen. Release candidate means it’s stable and (usually) feature complete but could have bugs and needs testing before they launch it.
It’s still a misuse of the word - if your software needs testing it’s not a candidate you would release unless you’re a multi-billion gaming company or Cisco
Wiktionary: (software engineering) A version of a program that is nearly ready for release but may still have a few bugs; the status between beta version and release version.
Oxford: a version of a product, especially computer software, that is fully developed and nearly ready to be made available to the public. It comes after the beta version.
I couldn’t find more definitions from “big” dictionaries, but literally no definition I’ve seen agrees with you. I wonder why that is.
KDE has a predefined schedule for “release candidates”, which includes RC2 later this month. So “RC1” is clearly not going to be the final version. See: community.kde.org/…/February_2024_MegaRelease
This is at least somewhat common. In fact, it’s the same way the Linux kernel development cycle works. They have 7 release candidates, released on a weekly basis between the beta period and final release. See: www.kernel.org/category/releases.html
In the world of proprietary corporate software, I more often see release candidates presented as potentially final; i.e. literal candidates for release. The idea of scheduling multiple RCs in advance doesn’t make sense in that context, since each one is intended to be the last (with fingers crossed).
It’s kind of splitting hairs, honestly, and I suspect this distinction has more to do with the transparency of open-source projects than anything else. Apple, for example, may indeed have a schedule for multiple macOS RCs right from the start and simply choose not to share that information. They present every “release candidate” as being potentially the final version (and indeed, the final version will be the same build as the final RC), but in practice there’s always more than one. Also, Apple is hardly an ideal example to follow, since they’ve apparently never even heard of semantic version numbering. Major compatibility-breaking changes are often introduced in minor point releases. It’s infuriating. But I digress.
I game, like a lot, and if windows beats me one more time i swear I’ll leave them for good. Is there a list of supported games? I just hit their site and only saw an nvidia gpx drivers too, did i simple miss the AMD stuff?
Intel and AMD drivers are part of the Linux kernel so you never need to think about drivers.
Check out https://www.protondb.com/ for something of a list of supported games, but generally most games just work (in Steam, go to Settings, Compatibility, and check the box for applying Proton on all games in library and not just the officially supported ones).
ProtonDB isn’t a complete list, but if you do struggle with getting a game to work, chances are somebody has posted a string you can paste into Steam to make the game magically work.
to add on to this, generally the only games that have issues are games with pretty serious anti cheat, and even many of those will still work. protondb will reflect this of course, but if you already know you mostly only play single player or cooperative titles, you can save a lot of time looking through your library
I appreciate what glorious eggroll does. And I’ve had no issues with the few games I’ve played on Steam.
I’ve been running Nobara for several months and it has been very stable though I find it is lacking a little polish around the edges in some areas. Kind of like how Mint was when I first started about 10y ago.
I’m trying out Fedora now for a while. On kernel 6.5. I was on 6.1 in Nobara. I have one game that’s crashing now (it wasn’t crashing in Nobara … go figure). So I may have to go back to Nobara or try to figure out what they did with Nobara vs Fedora that would help.
When Mint gets to kernel 6.x some day, I might jump back. (5.19 doesn’t support my GPU). Overall Mint became very polished. I hardly ever ran into weird issues. Although I do remember feeling Cinnamon blew up every so often.
I’d recommend Zorin. It has a UI similar to windows, easy to get into, great defaults, and being based on Ubuntu, most help on the internet will work just fine
Neither, the title specifically states Anarcho-Communism, not Marxism-Leninism. Closest analog would be any other AnCom that created a large publicly available service.
please please please avoid an LTS (long term support) distro for desktop use, especially if gaming. this includes Linux mint which is based on Ubuntu LTS. the packages are painfully old and cause problems playing the latest games, particularly where they don’t work out of the box with lutris/proton/wine etc. LTS is great for servers and workstations but not end users
experienced users can make any distro work including LTS but it’s extra overhead for new folks
It’s not about Laptop vs worksation. It’s about how new is the Hardware compared to the Linux Kernel shipping with the LTS distribution. If your hardware is older than the kernel, you will most likely not have any problems. For example, let’s say you use Ubuntu 22.04 LTS, which ships with Kernel 5.17 releaed in may 2022, if your computer is made of parts released in 2021, no problem.
OP, this is terrible advice. Do not follow! Unless you run into a problem with Ubuntu LTS or distro based on it that you and the community cannot solve and it’s due to the LTS, stick with LTS. The vast majority of users are on LTS which is why there are tested solutions for most common problems you might run into. LTS releases last for many years so once you solve a problem, it’s likely you won’t have to solve it again for a long time, unless you decide to make your life more interesting by upgrading or changing the OS. Non-LTS releases last for 9 months or so, then you’re thrust onto a new set of changes and bugs that may or may not hit you, with much fewer comrades to test them and find solutions for. As a new user, if you’re going with Ubuntu or Ubuntu-based OS, stick to LTS. You’ll have enough hurdles to cross getting acquainted with the OS itself.
my lug tries to help people trying to run lutris on old LTS versions and for one example we ended up having to tell them to use some .deb for lutris since ubuntu shipped a broken lutris version for a year or whatever users should always be able to depend on their package manager alone instead of side loading content. even had instances of their version of wget or curl being incompatible with winetricks and gitlab and githubs apis
Being able to always rely on the package manager alone, in other words on the built-in repos alone, has never been achievable on a stable system. You have to throw stability out of the window to allow for that to happen. There are huge downsides to that, especially for new users who have no clue how to isolate and work around defects. That’s why sideloading content via third party repos or individual debs has always been a part of the reality of Debian-based OSes. As a result, most open source communities and proprietary vendors provide one or the other.
Handles graphics drivers, printer drivers, looks like a windows without the influence of advertisers, what I consider a consistent theme, and best of all it is mind numbingly boring. Prepare yourself for the heart pounding activity of predictable updates, uncomplicated booting, running familiar applications, doing work, being productive, not even actively thinking about your OS.
Before Chromebooks, my towns school system had netbooks which were pitifully slow on Windows. They installed Ubuntu instead. The netbooks still sucked, but probably sucked a lot less.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.