Oh how quickly people forgot about Plasma 4. When a Debian stable is released with Plasma 6 then I’ll know it’s ready for me. I don’t rush into major KDE releases anymore.
My point was more that it was a very rough release even for a .0 and the distros should have waited a bit longer before shipping it as a default. All said I <3 KDE and have been using it since 0.9.6 I think
Debian sid user here. If it appears now or in two weeks in the repo does not change anything for me as I don’t depend on the changes for my workflows. For Debian Stable I actually demand them to come much later, in a mostly bugfree version. What’s the rush when it probably needs more field-testing?
I’m a Linux noob, I bought a refurbished Thinkpad to prepare myself for doing that. Been using that as much as I can for personal stuff while I experiment with running some of the more resource heavy programs I use in MS.
I have used a rasbpi with octoprint as a local server for CNC stuff, but that didn’t take much configuration.
What you claimed is that the fact that Debian repos move slowly (one of the key defining features of the distro) is a “niche” fact to Debian noobs (people who are new to using Debian).
TIL the only reason to mock a meme is if you’re upset, you can’t just think the meme is half-baked and joke about it. (Even if you upvote it because you did chuckle you’re still just upset).
You strike me as a true Linux master with 0 people skills.
I mean, the point of Debian is stability. If I’m running Debian then I’m not even gonna want to try and install the thing until after I’ve seen 100 people use it. I don’t think they’ll be looking for it in repos.
Both of you misunderstand the point of Debian’s stability.
When I run Debian Stable I want to be sure nothing changes about how the system works, until I have time to plan an upgrade.
So KDE6 could have literally zero bugs and it still wouldn’t make sense to push it into a current Debian release, because it has new features.
I think backwards compatibility is the keyword here. That would be the biggest requirement to allow updates.
New bugs, and maybe for example new hardening policies needed, could be another one. Maybe a future firefox implements feature x and you want to / have to disable that.
But at the same time Firefox is the best example of upstream doing the versioning. They know when to freeze features and likely backport every security critical issue. Thats not the case with many other packages debian ships, where it just doesnt ship updates whatsoever.
In about 2 years. By that time it will actually be stable and pretty much bug free. For me Debian is the only distro that provides a reliable experience.
Well I don’t actually use KDE. I just am stating what I’ve noticed in the past. KDE doesn’t have stability as a priority so using old versions is really the only way to not have bugs.
Though, I know of and have reported a ton of bugs “Resolved in Plasma 6”, where backports would make no sense as these architectural changes where so big.
There is an atomic image ready ,it still uses GDM (display managers are more complex to implement than you think) and I have the feeling it cant be the latest stuff, because it feels very incomplete.
Things like a populated dock etc are all missing, its upstream COSMIC.
Also there is no SELinux support yet, you can run it in permissive mode and should get all the errors needed to create one.
The FOSS community was doing fine with BSD and GNU v1 & v2, maybe the odd MIT licenses for decades. Or, decade. Or both. Or neither, if thats your bent. They were substantially similar: here’s the code, this is the license. You may modify the code hut not the license, and any derivative code must contain the original license. Oh and it has to include the code. Some allowed for commercial use, some did not. Not everybody liked that.
Then one day someone, I think it was Apache, decided no these terms don’t work for us, we don’t like to release the code and we want commercial use and to sell support. So they cut a new license. Not everybody cared, and Apache was happy.
Likewise, GNU foundation decided they wanted to compete in commercial space and allow for commercially supported releases, allowing .COMs to make money using and supporting what used to be FOSS. GNUv3 license got issued. Most of everybody who cared didn’t like that, but at least IBM, Oracle and Amazon are happy.
And then suddenly everyone was cutting their own licenses, and people who cared kinda gave up on it and went with what works.
Eventually, the people behind Wikipedia and the mediawiki software decided the People needed a license, so the Creative Commons license was born. I’m not well read in it, but I gather it us favorable for content producers, and is aaserted in “arenas of public discourse” (my own term) where content derives from individual contributors mostly as prophylaxis against trawlers, scrapers, aggregators and (to be tested,) LLMs.
Of course, asserting the license and defending against contrary use of the content is incumbent on the licensor, and must be defended in civil court. Not everybody can afford a lawyer, and EFF and the Open Source Initiative aren’t rich enough to litigate everything pro bono.
Any or all of the preceding might or might not be bullshit, but its my good faith read of the license shenanigans the last 10 years as I’ve bothered to pay attention to them.
I mean I get it might be because of being afraid of it being used to train LLMs. But I doubt that it would work, either because they won’t be used regardless or because of how federation works, i.e. literally it’d be more efficient if all of the known network instances’ operators somehow agreed to include/Lemmy, kbin and all of the microblogging platforms that can federate with Lemmy shipped a robots.txt that blocks known AI crawlers. Probably what would be more useful would be something that e.g. Akkoma and some other AP implementers offer, i.e. message autodeletion.
Also terrible if you want to retain any anonymity even if more people did it, because of stylometry.
If you’re using Debian stable, hopefully you fully expect and want not to get major software updates until long after they release, in exchange for a more predictable system.
I’m excited for Plasma 6 but I’m very willing to wait for it, and stick to 5.27 as a daily driver for the next year.
They might include it. Or they might not. If they don’t have time to test it, they just won’t, and you may wind up with 5.27 for longer than just the next year if you’re waiting for debian’s stable repos.
debian’s neovim is on version 0.7.2 (even in trixie/sid, you have to go to experimental to get to 0.9.5, which is the current). If there are any bugfixes between 0.7.2 and 0.9.5 that aren’t security backported… too bad. You aren’t getting it any time soon, because it’s not landing in Trixie, and it’s not guaranteed to land in whatever is after that either.
Debian’s “stable” refers to “predictable” like you said. Which includes bugs being predictable. Not resolved. Predictable. And if you have a bug that crashes your system, that bug will stay there unless it’s a “security” issue. Predictable crashing. NOT the “doesn’t crash” that people seem to think “stable” means.
I did. Something about the combination of Debian, KDE, Wayland and nvidia drivers made the system unstable.
After googling the issue for a bit, the consensus was that that just isn’t a good combination.
So I switched distros and now everything works.
Add comment