From: Nils Gillmann <gillmann@infotropique.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Guix on android blog post
Date: Tue, 1 May 2018 14:11:20 +0000 [thread overview]
Message-ID: <20180501141120.ynx7m5j3rlp2m4ow@abyayala> (raw)
In-Reply-To: <20180427052745.pf5cqufvdsxzlhxg@thebird.nl>
Pjotr Prins transcribed 495 bytes:
> On Tue, Apr 24, 2018 at 05:12:34PM +0530, Pierre Neidhardt wrote:
> > This is gold!! Thanks so much for sharing.
>
> Totally agree. Great work Julien a.o. Praphrasing one of the greats:
> what works on large systems tends to work on small. With minimized
> size packages Guix is quite ready to take on mobile and embedded
> systems in, typically, proprietary software environments. That is a
> huge market. We should be able to find companies interested in
> pitching in once they realise the benefits.
>
> Pj.
>
I think we should clarify "embeded" here. The size Guix itself
comes with is far from ready (probably never, not in the near future)
for real embeded devices. I think you all understand what we mean
when embeded is mentioned here.
Let's call them "small devices", and celebrate once someone in our
community manages to make Guix run on an actual embeded device with less
than 1MB. Even on my routers at home this is an impossible thing at the
moment.
Of course it would be great to have at some point, even if it would just
be a Proof of Concept.
next prev parent reply other threads:[~2018-05-01 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 8:26 Guix on android blog post julien lepiller
2018-04-24 11:42 ` Pierre Neidhardt
2018-04-24 12:17 ` julien lepiller
2018-04-24 15:02 ` Ricardo Wurmus
2018-04-24 15:28 ` julien lepiller
2018-04-24 12:18 ` Adonay Felipe Nogueira
2018-04-27 5:27 ` Pjotr Prins
2018-05-01 14:11 ` Nils Gillmann [this message]
2018-05-01 10:26 ` pelzflorian (Florian Pelz)
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=20180501141120.ynx7m5j3rlp2m4ow@abyayala \
--to=gillmann@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).