Yeah, but that’s exactly the meme that I’m talking about.
It’s always ambiguous what is meant by stability. And as soon as you complain about Debian actually breaking very easily, folks will readily tell you about the technicality that it just means it doesn’t change very often.
Having btrfs+snapper set up by default sounds good. I wish Debian-based distros in general would finally make a move there. It’s a bit of a meme that folks laud Debian for its stability, but you can easily break it with one wrong command.
And who knows, maybe TuxedoOS adopting it can serve as a proof of concept and get Debian itself to adopt btrfs sooner.
More of a general tip: https://reuse.software/ can help to get this stuff right.
Pretty sure, it won’t be able to help with your use-case of copy-pasting code snippets, though (it’s not at all trivial to know which parts you copy-pasted), but it gives you a structure to work with and can automatically annotate new source files.
Yeah, we’re also still on 24.04. And from what I’ve seen, 26.04 will ship with Plasma 6.6, not 6.7.
Maybe the kubuntu-backports repository can give it earlier than that, but yeah, I don’t even know yet, when we’ll upgrade to 26.04.
Good point, though, about the .01 release. Maybe I’ll start bothering IT when that’s out.
I would have a use for it at $DAYJOB, but unfortunately my work laptop is on an ancient version of Ubuntu, so gonna be a few more years before I can use it…
Gonna throw in EtherPad. It’s been like ten years, since I properly used it, but I believe, it’s relatively minimal, so pretty much just Markdown.
There’s also lots of publicly hosted instances you can use: https://scanner.etherpad.org/
Oh, huh, I saw the release announcement for Fedora 44 explicitly mention Plasma 6.6, so I figured it was tied to the release. 🫠
Yeah, it should come with the next Fedora release, which is scheduled for October 20th.
Feature updates, like this new Plasma version, get shipped every half year on Fedora. In between, you mostly just get security and bug fixes…
I find that setting the power profile to “Power-Saver” makes a huge difference.
KDE has support for that built-in, although I’m not sure, if distributions install the corresponding daemon on desktop systems: https://gitlab.freedesktop.org/upower/power-profiles-daemon
You should be able to cycle through power profiles with Meta+B on KDE.
You can also see and change the profile via the systray icon for the battery, but on a desktop system, that presumably won’t be shown by default.
Otherwise, powerprofilesctl is also an option, as described in that link.
It was one of the stated goals for Servo itself to be designed like that. But I don’t think anyone at Mozilla expected Servo to take over from Gecko. They were already quite happy that they were able to incorporate Servo’s style engine and URL bar implementation and such into Gecko.
I don’t think that’s quite right. The Linux kernel, Firefox and Chromium all sit around 30 millions lines of code, last I checked, so if you add the rest of the operating system, it should still have more lines of code than the browser.
But yes, similar order of magnitude.
Hmm, seems to work like you want for me. Using Plasma 6.6 with the icons-only task manager…
Should perhaps add that you can generally run Linux distributions off of a USB stick for that first impression.
Just follow a tutorial for how to install Linux and when you see the actual installer on screen, you can just close the installer without installing and then click around in the UI.
It will be slow, because it’s running off that slow USB connection, but otherwise this is pretty much the operating system as it is when fully installed.
Alt+F3 can also work (possibly in addition to Alt+Space)…
Same. For whatever reason, I kind of hate all cursor themes. I disliked Breeze the least, then thought about how I’d want to change Breeze to improve it, realized that would look much worse, and since then I’ve been content with Breeze.
Nah, you can have a license that says you get a cupcake and another license that says you need to give up your first-born.
And then you can mush those licenses to say that you need to give up your first-born, but you get a cupcake in return.
Unless the specific license terms contradict, this is totally possible.
AGPL is specifically for web services. For example, if Nextcloud were provided under the GPL, Amazon or the like could serve a modified version of Nextcloud without having to hand out their modifications. As far as the GPL is concerned, Amazon is the user and the software just happens to accept requests from the network.
With AGPL, those who use the software over the network are also deemed users and therefore have the right to access the source code.
I imagine, the scenario would be that the cloud service links against a library under the supposed new license.
And then, even if you’re just using the cloud service over the network, you can demand changes to the source code of that library to be open-sourced.
I imagine, it’s just too much of a niche and practically not enforceable anyways.
You would need to somehow know that a web service is a using a modified version of your library, then you’d be able to demand those library changes to be open-sourced.
And well, just in general, covering all kinds of niche use-cases isn’t terribly healthy for open-source licenses, because each modification is something that can be challenged in court and which might be incompatible with other licenses.
Ultimately, a library under such a specialty license would probably not see much use either. You could only really depend on it in AGPL applications. And at some point, you do have to ask yourself, if it’s even useful to develop your library then.
Well, in hopes that you’re not just trolling, maybe you’ll believe a dictionary that “stable” is ambiguous in this context. Because this is one of the listed meanings:
https://en.wiktionary.org/wiki/stable#Adjective
It also lists your meaning. I’m not saying that you’re wrong. I’m saying it’s ambiguous, i.e. there’s two meanings that could apply here.
Well, and personally, I do feel like more people will interpret “stable” to mean bug-free here, because Debian is a piece of software to them.