- 1 Post
- 13 Comments
Debian. Because it’s the best about “Just Works” (yes, even moreso than Ubuntu, which I tried). It has broken once on me, and that was fixed by rolling back the kernel, then patched within the week.
BUT I’m also not a “numbers go up” geek. I don’t give a shit about maxing out the benchmarks, and eking every last drop of performance out of the hardware; to me, that’s just a marketing gimmick so people associate dopamine with marginally improved spec numbers (that say nothing about longevity nor reliability).
If you wanna waste something watching numbers go up, waste time playing cookie clicker, not money creating more e-waste so your Nvidia 4090 can burn through half a kilowatt of power to watch youtube in 8k.
(/soapbox)
My gpu is an nvidia 970 and my cpu is a 4th or 5th generation core i7. I just don’t play the latest games anyway, I’m a PatientGamer, and I don’t do multimedia stuff beyond simple meme edits in GIMP.
It has plenty of power to run VMs, which I do use for my job and hobby, and I do coding as another hobby in NVIM (so I don’t have to deal with the performance penalty of MS Code or other big GUI IDEs).
It all works fine, but one day I’ll upgrade (still a generation or two behind to get the best deals on used parts) and still not waste a ton of money on AAA games nor bleeding-edge DAWs
The cool thing about Arch is that with some learning, time and effort, you can make it function just like Ubuntu
false dichotomy. Sometimes people justifiably dislike something for reasons beyond elitism (e.g. Canonical is a for-profit corporation that muddies the waters of FOSS), but it’s also not just playful bants.
Also, as with every opinionated topic: do your own research and think critically. Don’t hate Ubuntu until you have tried it and have investigated those who maintain it. Don’t praise it until you do so either.
I don’t care if you come to a different conclusion than me, as long as you didn’t just function on the “wisdom of the crowd”
When does Debian update a package? And how does it decide when to?
These both can be answered in depth at Debian’s releases page, but the short answer is:
Debian developers work in a repo called “unstable” or “sid,” and you can get those packages if you so desire. They will be the most up to date, but also the most likely to introduce breaking changes.
When the devs decide these packages are “stable enough,” (breaking changes are highly unlikely) they get moved into “testing” (the release candidate repo) where users can do QA for the community. Testing is the repo for the next version of debian.
When the release cycle hits the ~1.5 year mark, debian maintainers introduce a series of incremental “freezes,” whereby new versions of packages will slowly stop being accepted into the testing repo. You can see a table that explains each freeze milestone for Trixie (Debian 13) here.
After all the freezes have gone into effect, Debian migrates the current Testing version (currently Trixie, Debian 13) into the new Stable, and downgrades the current stable version to old-stable. Then the cycle begins again
As for upgrades to packages in the stable/old-stable repos: see the other comments here. The gist is that they will not accept any changes other than security patches and minor bug fixes, except for business critical software that cannot just be patched (e.g. firefox).
2·1 month agothose still require root, they just don’t explicitly say so. They still pop up with a password prompt
Jump ship. If you can make do without windows, do so. It takes away so much of the frustration, and you just learn to let it go when devs won’t make linux-compatible binaries: after all, it’s basically them telling you they need to be able to spy on you, so why use their app?
Funny you should say that, because…
To the feature creep: that’s kind of the point. Why have a million little configs, when I could have one big one? Don’t answer that, it’s rhetorical. I get that there are use cases, but the average user doesn’t like having to tweak every component of the OS separately before getting to doom-scrolling.
And that feature creep and large-scale adoption inevitably has led to a wider attack surface with more targets, so ofc there will be more CVEs, which—by the way—is a terrible metric of relative security.
You know what has 0 CVEs? DVWA.
You know what has more CVEs and a higher level of privilege than systemd? The linux kernel.
And don’tme get started on how bughunters can abuse CVEs for a quick buck. Seriously: these people’s job is seeing how they can abuse systems to get unintended outcomes that benefit them, why would we expect CVEs to be special?
TL;DR: That point is akin to Trump’s argument that COVID testing was bad because it led to more active cases (implied: being discovered).
“I am a new linux user. After 15 minutes of research on google, I found a few forum posts and some niche websites that said SystemD was bad, so I took it as gospel. Now my system doesn’t work as simply as it did with installer defaults? How do I make everything Just Work™ after removing any OS components I don’t understand the need for?”
was that translated into english from another language?
I love how they blended FAQ with meth-induced psychosis rambling.
I’ve gotta give them kudos for sticking to their very strict values, but holy hell is this hard to parse