Originally posted by DanL
View Post
Announcement
Collapse
No announcement yet.
Linux Mint 20 Doing Away With 32-Bit Support
Collapse
X
-
Originally posted by NotMine999 View PostI run the few (3) desktops that I have on Debian Testing so I can do some of the stuff that the kewl kids do. And I don't mind spending a little bit of time fixing them when they get goofy due to a package update; what I learn on 1 I can apply to the other 2. After all, M$ Windoze has taught us that desktops are for fiddling after the updates are done.
I don't think most will like to use a Linux desktop OS that is kind of like that.
Comment
-
Originally posted by Weasel View PostI see nothing about that on the official blog post. So that's pure speculation.
Comment
-
Originally posted by starshipeleven View PostOne of the reasons people are fleeing Windows is this bs of fiddling to fix things after updates
I don't think most will like to use a Linux desktop OS that is kind of like that.
I would add that some people want/need "cutting edge" features and thus require a "cutting edge" version of an OS to get support for those desired features. Expecting their OS choice to perform like a "stable" OS would is simply not rational.
I seem to remember Windoze 10 implementing something like: (1) a cutting edge release (latest & greatest at the expense of stability); (2) a business-oriented release with less frequent updates (stability at the expense of eventually getting the latest & greatest feature in the future); and (3) something in-between (1) and (2) that compromised some "cutting edge" aspects for better stability. Choices, choices, but at least you got choices to consider.
As for Debian, as you probably know, they have something like the release approach that Windoze 10 uses. On my systems that run Debian Testing I find them to be stable for their intended tasks (nothing truly "cutting edge" in my case). Past experience has shown me that Debian Testing has caused me to have to "fix it" perhaps once or twice between it's introduction as "testing" and it's "blessing" as "stable". Not a bad "fix it" rate; actually acceptable to me. If I don't want any "fix it" sessions then I opt for "stable" (stability at the expense of "cutting edge", aka choice 3 from above).
IMHO software stability does not simply occur straight out of the compiler; programmers are not perfect, and bugs find creative ways to manifest themselves. Even Linus runs a Linux release through a few RC versions before blessing a release version. I used to write software for internal company use and I found it had always had a bug or 3 once I finished the coding, so I learned to test it 2 or 3 times and increasing larger user groups before calling it "production".
Said another way with an old saying: "You pays your money and you takes your chance."
Comment
Comment