unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: guix-devel@gnu.org
Subject: Guix size reduction work group
Date: Tue, 04 Feb 2020 16:57:17 +0100	[thread overview]
Message-ID: <87pneul50i.fsf@ambrevar.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Hi!

At FOSDEM 2020 Ludovic explained to the world why Guix is better than
other container formats (to put it mildly ;p).

Possibly the only counter-argument to "Guix  > Snap / Flatpak" is
the size of the Guix containers.

I also talked to Mathieu who has been working relentlessly on
cross-compilation and embedded device support recently.  He gave a
presentation on Guix vs. Yocto at FOSDEM.  But again, the main
counter-argument is that Yocto allows for much smaller systems.  (I
think Mathieu has some figures.)

Shall we start a work group to fix the issue?

- Write a blog article to explain the issue and a detailed process on
  how to fix it.  (Embed it to the manual.)

- Improve the tooling.  In my experience, guix graph is quickly unusable
  with a high number of nodes.  Maybe d3.js could be leveraged to add a
  filtering system, or a way to click on nodes to hide them and all
  their children.

- How do we compare to Nix?

Other suggestions?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

             reply	other threads:[~2020-02-04 15:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:57 Pierre Neidhardt [this message]
2020-02-04 16:22 ` Guix size reduction work group zimoun
2020-02-04 17:59   ` Julien Lepiller
2020-02-05 15:18 ` Ludovic Courtès
2020-02-05 16:11   ` zimoun
2020-02-07 21:35     ` Ludovic Courtès
2020-02-07 22:31       ` Gábor Boskovits
2020-02-08 13:40         ` zimoun
2020-02-10 13:13       ` Tobias Geerinckx-Rice
2020-02-11 14:15         ` Ludovic Courtès
2020-02-08 16:43   ` Pierre Neidhardt
2020-02-09 23:45     ` zimoun
2020-02-10  8:09       ` Pierre Neidhardt
2020-02-10  8:46         ` Christopher Baines
2020-02-11 14:17           ` Ludovic Courtès
2020-02-10 10:30         ` zimoun
2020-02-10 12:33         ` Julien Lepiller
2020-02-11 14:20     ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87pneul50i.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).