all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Distopico <distopico@riseup.net>
To: Wilko Meyer <w@wmeyer.eu>
Cc: guix-devel@gnu.org
Subject: Re: Guix and the developer ecosystem
Date: Fri, 04 Aug 2023 20:40:05 -0500	[thread overview]
Message-ID: <87leeqmf8g.fsf@riseup.net> (raw)
In-Reply-To: <87o7jrg9ih.fsf@wmeyer.eu>

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


On 2023-07-31, Wilko Meyer <w@wmeyer.eu> wrote:

> Hi,
>
> Distopico <distopico@riseup.net> writes:
>
>> 2. Do you see developers as a potential target audience for Guix, or is
>> it mainly focused on HPC (High-Performance Computing)?
>
> Developers is a pretty broad and generic term to start with. Considering
> Guix is somewhat of a general purpose package manager/Guix System a
> general purpose distribution, I think the better question to ask,
> instead of asking for target audiences, is, how and in what way Guix
> features and concepts can aid and help with hacking on software. HPC is
> an area where Guix can be put to good use, but it's also a reasoanble
> choice for other areas as well I'd argue.
>
I believe one area for improvement is the possibility of having tools
and the compiler sharing common ground. For example, rust-1.6 with
rust-analyzer-1.6 with version 20220809 and rust-1.7 with
rust-analyzer-1.7 with version 20230911. In that case, similar to
rustup, we could do guix shell rust@1.6.8 rust-analyzer@20230911. In
Haskell, a similar issue occurs, where haskell-language-server, e.g.,
version 1.3, only works with specific GHC versions.

> IMHO Guix has plenty of useful features that, in my opinion, can be put
> to good use in the process of developing software. I *mostly* work with
> C and Rust, as well as Perl, and less frequently, Python and CommonLisp;
> so my experience with Guix is mostly limited to these languages.
>
How is your workflow with rust? I mean you use --container to just
download `rustup` and install it in the container?

> Using a guix.scm file for projects to provide a good way to spin up a
> development environment fast/to onboard new people, and make use of guix
> shell (mostly with --container) while working on software; are probably
> my most used features in that regards.
>

I do that as well, but in mostly of the cases just for me because other
team member can use it due is Gnu/Linux only, could be good have
something like emacs cross-platform.

> Best Regards,
>

Thank you for the reponse.

> Wilko Meyer


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

  reply	other threads:[~2023-08-05  1:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  0:29 Guix and the developer ecosystem Distopico
2023-07-29 19:48 ` Liliana Marie Prikler
2023-08-05  1:11   ` Distopico
2023-08-05 17:29     ` Liliana Marie Prikler
2023-08-05 19:48       ` (
2023-08-05 20:12         ` Liliana Marie Prikler
2023-08-08 16:59     ` Saku Laesvuori
2023-07-31  9:42 ` (
2023-08-05  1:49   ` Distopico
2023-08-05  6:10     ` Julien Lepiller
2023-07-31 18:55 ` Wilko Meyer
2023-08-05  1:40   ` Distopico [this message]
2023-08-16 14:22 ` Ludovic Courtès
2023-08-18 17:16   ` Distopico
2023-08-24 15:01     ` Ludovic Courtès
2023-08-29 18:42       ` Distopico
2023-08-19  8:29 ` Simon Tournier

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=87leeqmf8g.fsf@riseup.net \
    --to=distopico@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=w@wmeyer.eu \
    /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.