A bold claim. RHEL updates are mostly security patches, are they doing that due to lack of resources too? Is it that hard to imagine that enterprise distros don’t want surprises from changing functionality?
The word “stable” usually means unchanging through a release. I.e. functionality of one release is the same if you stay in that release even if you update (security and bug fixes mostly). The experience of the system not doing anything unexpected like crashing is reliability. A rolling distro is by that definition not stable, but it can be more or less bug free and crash free.
To me the issue is the people calling a system stable because it is reliable, even if it updates unpredictably to changing functionality.
Do you use your computer for things that rely on specific library versions and functionality?
Plan9 would have some opinions about that.
Well, it’s SVT, the swedish tax funded national tv. I think it’s more the case that they fundamentally don’t understand the people who were part of the Pirate Bay.
Vi and later editors added a lot of commands, but if you want to keep the spirit of ed(1) and bring it into a visual context, I’d say sam(1) is the true successor. It’s what Ken Thompson used after ed, and Brian Kernighan. There are some people who at least are interested in ed today, this book is good for example: https://www.tiltedwindmillpress.com/product/ed/
It comes with both fvwm and cwm, and you can install all the usual ones or a full desktop environment. Personally I like cwm in the minimalist end and xfce for more of a full desktop, but it’s all just preferences. Which one do you like in Linux?
OpenBSD is surprisingly good as a desktop, as long as you don’t need something that needs shoehorning in or some fancy filesystem. But if you use it as intended, it’s good. Like, there’s no linux compatibility, no proprietary nvidia drivers, etc. You probably want to switch away from the default window manager though unless you think perfection was reached in the early 90s.
This is why my preferred way of communicating is to sit in darkness and construct one-time pad ciphers which I then put in a new safe that I don’t have the combination to unlock and is welded shut and dropped into the ocean. But other than that I like to use grapheneOS and matrix. I can’t be sure it’s 100% private, but I am 100% sure that facebook isn’t private, so I’d rather use matrix.
Button2 and while pressed, button3 to snarf.
I just feel that it’s technically wrong to call it x64. x86 is the architecture. The x belongs there, so x86-64 makes more sense, but not “x64”. It’s a marketing term, but it still bothers me.
Isn’t “x64” still an x86 architecture?
The picture called “Upstream and Prism programs” has the old logotypes for Yahoo, Hotmail, etc, and the old garamond version of the google logo, they must have been doing this for a while.
And after you have learned Linux, download any distro that lets you work on your projects with the least hassle and get work done without fiddling around in every aspect of the OS. At least that’s what I’ve observed among older users who see the OS as a tool and not a hobby in itself.
The torso is a tricky concept, there’s no good anatomical definition that makes sense. Is the pelvis included? The whole axial skeleton? Everyone knows the general idea of where the torso is, but it’s hard to define with precision.
Peter Sunde said that the show is not a fair description of what happened and that it’s missing the focus on what was important.
How well do the hashtags work in practice on mastodon? Are they used as intended and actually useful?