discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Soeren Tempel <soeren@soeren-tempel.net>, discuss@mandoc.bsd.lv
Subject: Re: zstd compression
Date: Thu, 30 Jan 2025 10:59:41 +0100	[thread overview]
Message-ID: <Z5tNjZE0fPihyIPA@asta-kit.de> (raw)
In-Reply-To: <87wmeep1wj.fsf@gmail.com>

Hello Maxim,

thanks for explaining.  I see, "Guix System" is also an operating system,
which is not immediately obvious from the web page (but only becomes
clear after following the "about" link).  I now also understand that
some steps have been taken to mitigate some of the security implications
of the fundamental concept.  It all sound extremely complicated, which
is usually not very good for security - then again, this is probably
the usual tradeoff that every system has to make: OpenBSD leans towards
security and simplicity, Guix appears to lean more towards fancy
features at the expense of significant complication.

Anyway, i have now added Guix here:

  http://mandoc.bsd.lv/ports.html  # three place: overview, packages,
                                     maintenance
  http://mandoc.bsd.lv/porthistory.html  # two entries


Maxim Cournoyer wrote on Wed, Jan 29, 2025 at 03:30:52PM +0900:
> Ingo Schwarze wrote:

>> I feel serious tempted to rip out compression support altogether.
>> It's just so anachronistic.

> It costs relatively little in complexity,

As long as only one compression format is required, the complexity is
moderate, and that contributed to not being ripped out yet.  It gets
worse when different systems require different compression.

Let's wait for Soeren - if he manages to get the compat lib installed
as a shared object, then i can do the zstd thing in the upstream repo
as explained earlier, with the (small) additional complexity confined
to the configuration system, without invading the code.

[...]
> That's a 50 MiB space saving, which while not enormous is not nothing
> either, especially on a transactional system like Guix where you may be
> keeping multiple past versions of things with the space usage adding up.

OK, let's assume the worst: every user installs all the packages
you have on your system, but in such a way that no two users
install the same version of any package.  Then it boils down to
50 MiB per user, which i would indeed call "nothing".  I mean,
a few lines above, you talked about making it easy fur users to
compile chromium.  Compared to that, 50 MiB is absolutely nothing
indeed.  I think you can safely assume every user does at least
*something* that requires space in amounts typical for the 2020ies,
and compared to that, 50 MiB is nothing.

Or look at it the other way: how many users do you have on your
machine?  Two hundred, maybe?  In that case, you gain 10 GB.
On which modern machine that serves hundreds of users do 10 GB
of disk space matter?

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


  parent reply	other threads:[~2025-01-30  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  7:10 Sören Tempel
2025-01-28 10:40 ` Ingo Schwarze
2025-01-29 23:36   ` Alexis
     [not found]   ` <87wmeep1wj.fsf@gmail.com>
2025-01-30  9:59     ` Ingo Schwarze [this message]
     [not found]       ` <87v7tvoiqu.fsf@gmail.com>
2025-01-31 12:43         ` Ingo Schwarze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z5tNjZE0fPihyIPA@asta-kit.de \
    --to=schwarze@usta.de \
    --cc=discuss@mandoc.bsd.lv \
    --cc=maxim.cournoyer@gmail.com \
    --cc=soeren@soeren-tempel.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).