all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: david larsson <david.larsson@selfhosted.xyz>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org,
	Guix-devel
	<guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org>
Subject: Re: Building a software toolchain that works
Date: Fri, 18 Mar 2022 22:13:32 +0100	[thread overview]
Message-ID: <699ed5cd32d656ae03e05994026784e5@selfhosted.xyz> (raw)
In-Reply-To: <87ee3091ql.fsf@gmail.com>

On 2022-03-17 13:56, zimoun wrote:
> Hi Olivier,
> 
>> On another note, what I find fascinating is why Guix and Nix are not
>> more used in academic papers.
> 
> Indeed.
> 
> One part of the answer is, IMHO: it is difficult to spread the word.
> 
> For instance, with co-authors, we have tried to write a short paper
> detailing what Guix solves, i.e., the computational environment part of
> the “science crisis“, and targeting especially bioinfo folks.  We got
> many refusals by the journals that bioinfo folks indeed read and we end
> in a “specialized” journal.
> 
> On the top of that, add the fact that most of the time, people use what
> other people in their lab or collaborators already use.
> 
> On the top of that, add the fact that the story of Guix on Windows or
> Mac is not really good.  I am not arguing here, just to mention that
> many people are still using Windows or Mac and few one Linux variant.
> 
> Therefore, all in all, the bootstrap of Guix is hard; as always. :-)
> 
> The initiative Guix-HPC is an attempt to address that.  The name is
> probably not fully representative since now it looks like Guix in
> scientific context; HPC being only one component.
> 
> From my point of view, the bootstrap of Guix in scientific world
> requires more documentation materials for many common use cases and 
> more
> popular applications or usual scientific stack.  For instance PyTorch 
> in
> Guix is one step but many things are still really hard to do with Guix
> when it is not elsewhere.  Another instance is RStudio for bioinfo 
> folks
> – it does not work out of the box with Guix when it does elsewhere.
> 
> Help in these both areas – howto materials and popular applications – 
> is
> very welcome. :-)
> 
> Join the fun, join guix-science@gnu.org :-)
> 
> 
> Cheers,
> simon

I run Guix including GUI applications from Windows via WSL2 (Windows 
Subsystem for Linux). It may help some to try it out if this setup was 
easier and more documented, though I suppose that is somewhat prevented 
to go via official channels by the FSDG guidelines.

Best regards,
David


  reply	other threads:[~2022-03-18 21:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 19:05 Building a software toolchain that works Ryan Prior
2022-03-14 20:26 ` Pjotr Prins
2022-03-14 21:40   ` David Arroyo
2022-03-15  8:19     ` Ludovic Courtès
2022-03-17  9:20       ` zimoun
2022-03-16 14:02     ` Josselin Poiret
2022-03-16 15:28       ` Ryan Prior
2022-03-16 20:13         ` Yasuaki Kudo
2022-03-17 15:35     ` Maxime Devos
2022-03-17 16:56       ` David Arroyo
2022-03-14 23:57   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-15  8:23     ` Ludovic Courtès
2022-03-15  8:42       ` Pjotr Prins
2022-03-15 12:32       ` Yasuaki Kudo
2022-03-17 12:56     ` zimoun
2022-03-18 21:13       ` david larsson [this message]
2022-03-18 23:59         ` Yasuaki Kudo
2022-03-19 13:02         ` Windows Subsystem for Linux zimoun
2022-03-24 21:14           ` Ludovic Courtès
2022-03-25  3:43             ` Maxim Cournoyer
2022-03-25  9:04               ` Phil
2022-03-25 10:14                 ` Oliver Propst
2022-03-17 20:04   ` Building a software toolchain that works Katherine Cox-Buday
2022-03-18  6:27     ` Pjotr Prins
2022-03-18  9:10       ` Oliver Propst
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 12:06 zimoun

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=699ed5cd32d656ae03e05994026784e5@selfhosted.xyz \
    --to=david.larsson@selfhosted.xyz \
    --cc=guix-devel-bounces+david.larsson=selfhosted.xyz@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.