From: Alex Vong <alexvong1995@gmail.com>
To: Adam Van Ymeren <adam@vany.ca>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Guix libification.
Date: Sun, 11 Jun 2017 15:19:06 +0800 [thread overview]
Message-ID: <87mv9f9el1.fsf@gmail.com> (raw)
In-Reply-To: <2D5D3EC0-B9B1-462D-BE9B-0C0E20F336EC@vany.ca> (Adam Van Ymeren's message of "Sat, 10 Jun 2017 12:32:07 -0400")
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Adam Van Ymeren <adam@vany.ca> writes:
> On June 10, 2017 12:04:59 PM EDT, Alex Kost <alezost@gmail.com> wrote:
>>
>>I also needed similar functionality, but since I didn't want to depend
>>on guix modules
>
>
> Why not depend on guix modules? I'm not a scheme/guile expert just
> curious, what's the downside to depending upon guix?
I can think of many problems.
Conceptual problem: Guix is a package manager, not a library. It is
akward to depend on a package manager, not using it for package
management, but to use the data structures it provides.
Size problem: Guix is not small. If you software is simple and small,
depending on guix will make your software signaficantly bigger.
API stability problem: Guix has no stable API. This is to make
development easier. Maintaining old stuff just to keep backward
compatibility requires a lot of effort. Depending on guix means your
application will break if guix decides to change its data structure
API.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-11 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 10:08 Guix libification Mathieu Othacehe
2017-06-10 14:42 ` Mike Gerwitz
2017-06-10 16:04 ` Alex Kost
2017-06-10 16:32 ` Adam Van Ymeren
2017-06-11 7:19 ` Alex Vong [this message]
2017-06-12 16:53 ` Alex Kost
2017-06-11 14:24 ` Ludovic Courtès
2017-06-11 17:56 ` Jan Nieuwenhuizen
2017-06-11 20:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv9f9el1.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=adam@vany.ca \
--cc=alezost@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.