<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><font face="Tomson Talks">William Park
via kwlug-disc wrote on 2026-06-22 11:19:<br>
</font></div>
<blockquote type="cite"
cite="mid:911eda13-7fcb-4d2e-852e-8871b5e48eb3@yahoo.ca"><font
face="Tomson Talks">Since lots of people here are going ga-ga
over immutable os...<br>
</font>
<blockquote><font face="Tomson Talks"><a moz-do-not-send="true"
href="https://distrowatch.com/dwres.php?resource=showheadline&story=20206">https://distrowatch.com/dwres.php?resource=showheadline&story=20206</a><br>
</font> <font face="Tomson Talks"><a moz-do-not-send="true"
href="https://blog.woralelandia.com/ten-1-reasons-to-avoid-the-immutable-desktop-en.html"
class="moz-txt-link-freetext">https://blog.woralelandia.com/ten-1-reasons-to-avoid-the-immutable-desktop-en.html</a></font></blockquote>
</blockquote>
<p><font face="Tomson Talks">I have had about zero interest in an
immutable OS, but Linux Unplugged podcast had an episode on the
new KDE Linux, which is immutable, and they heaped a lot of
praise on it.</font></p>
<p><font face="Tomson Talks">Since KDEneon is likely to go away at
some point, their review made me add KDE Linux to the possible
replacements. We'll see.</font></p>
<p><font face="Tomson Talks">(Edited to add: Just saw Doug's post
about immutable vs atomic, something I wasn't aware of. Not sure
which KDE Linux is.)</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">As to the article..</font></p>
<p><font face="Tomson Talks">I agree the concept seems most relevant
to kiosks & appliances.</font></p>
<p><font face="Tomson Talks">But I don't think it's fair to ignore
the growing number of users who do not want to tinker, just use
their computer as a tool. And for them, the ability to roll back
to an un-borked state is invaluable.</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">> </font>standardizing the exact
same OS image across millions of installations creates a
beautiful, uniform monoculture. If a zero-day is found in that
specific image, every single user on Earth gets compromised by the
exact same payload.</p>
<p><font face="Tomson Talks">I mean, isn't that how any distro has
always worked? Fedora gets hit by a zero-day, every single
Fedora user on Earth gets compromised? Not really seeing value
in his point, even when he clarifies with "state drift" (all
installs being slightly different due to user chosen suite of
apps & libraries)</font></p>
<p><font face="Tomson Talks">His "state drift" as security mechanism
isn't compelling to me.</font></p>
<p><font face="Tomson Talks">Plus, let's just ignore how many bug
reports "state drift" causes maintainers when it's more a user
issue (why did you upgrade the underlying version of Python?!?
That breaks `apt`, etc.)</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">Then, he decided to make his embellish
his point by making creepy faces at me (winkie face!!1!) and ...
I'm out.</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">Okay, one more, paraphrasing:</font></p>
<p><font face="Tomson Talks">> /usr may be protected but $HOME is
not: check mate</font></p>
<p><font face="Tomson Talks">So ... no reason to protect /usr?
$HOME should be protected too? I dunno, I'm not liking the logic
here.</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">I'm not enthusiastic about immutables,
but am willing to see more about KDE Linux before I outright
reject the possibility of running one.</font></p>
<p><font face="Tomson Talks">I would consider recommending them to
less technically savvy users.</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
<p><font face="Tomson Talks">(Now, having written all that prior to
Doug's post, I need to go back and watch his presentation.)</font></p>
<p><font face="Tomson Talks"><br>
</font></p>
</body>
</html>