all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Phil <phil@beadling.co.uk>, "Ludovic Courtès" <ludo@gnu.org>,
	"Benjamin Slade" <beoram@gmail.com>,
	help-guix@gnu.org
Subject: Re: Enterprise Guix Hosting?
Date: Fri, 26 Aug 2022 15:40:21 +0900	[thread overview]
Message-ID: <863E65DC-345E-47FF-8031-6CA897C451E9@yasuaki.com> (raw)
In-Reply-To: <87mtbsi2yx.fsf@laura>

And I recently experimented with WSL2 and WSLG on Windows 11, running on a 5-year-old Surface Book.

Ubuntu works quite well on it and I can run Linux GUI applications from Windows and run Windows applications, like Excel and Powershell, from Linux.

So this indicates there is a high likelihood Guix will be a decent enterprise package manager, as long as the users' IT department allows WSL on enterprise-managed Windows PCs.  (which may be a hurdle too much to ask for though😅)

Sorry I have been wanting to follow up more but I have been too busy setting up our worker coop in Japan😅

-Yasu


> On Aug 26, 2022, at 03:37, Olivier Dion <olivier.dion@polymtl.ca> wrote:
> 
> On Mon, 15 Aug 2022, Phil <phil@beadling.co.uk> wrote:
>> Yasuaki Kudo writes:
> 
>> However, I am interested in seeing Guix and Guix services
>> gaining a foothold in the commercial space, and exchanging ideas
> 
> I see a lot of potential there:
> 
>  - Continuous integration
>  - VM generation and deployment with OpenStack
>  - Container generation and deployment with K8s
>  - Root filesystem generation for embedded systems (e.g. Yocto, Elbe)
> 
>> as well as growing it in academia too.
> 
> As a student, here's how I have been using Guix on the academic side:
> 
>  - CI (cuirass) of developed tools
>  - Reproducible workflow for my research
>  - guix-shell + manifests for volatile laboratories environment
>  - Automatic correction of student's work submission (similar to a CI)
> 
> In all, Guix is a very powerful/flexible tool when in good hands and
> everyone in the field would gain from mass adoption of it.  I think it
> has a bright future ahead.
> 
> -- 
> Olivier Dion
> oldiob.dev


  reply	other threads:[~2022-08-26  6:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via
2022-07-30 16:20   ` Phil
2022-07-30 23:18     ` Yasuaki Kudo
2022-07-31  0:42       ` Benjamin Slade
2022-07-31 11:01         ` Phil
2022-08-09 20:37           ` Ludovic Courtès
2022-08-09 22:24             ` Yasuaki Kudo
2022-08-14  9:53             ` Phil
2022-08-14 22:03               ` Yasuaki Kudo
2022-08-15 20:50                 ` Phil
2022-08-25 18:37                   ` Olivier Dion via
2022-08-26  6:40                     ` Yasuaki Kudo [this message]
2022-10-12  9:55                     ` Ade Malsasa Akbar
2022-10-12 10:18                       ` Olivier Dion via
2022-08-26  7:24                 ` Ricardo Wurmus
2022-08-31  1:42                   ` Thompson, David
2022-08-31  6:33                     ` Ricardo Wurmus
2022-08-31 10:46                       ` [EXT] " Thompson, David
2022-08-31 11:42                         ` Olivier Dion via
2022-08-31 12:54                           ` Thompson, David
2022-09-05 19:38                         ` [EXT] " Ludovic Courtès
2023-01-23 15:34                           ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Giovanni Biscuolo
2023-01-23 16:48                             ` Przemysław Kamiński
2023-01-23 17:59                               ` Wojtek Kosior via
2022-09-05 19:42               ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03               ` zimoun
2022-10-08 16:23                 ` Phil
2022-10-10  7:58                   ` zimoun
2022-10-10 10:30                     ` (
2022-10-10 10:49                       ` zimoun
2022-10-10 19:35                     ` Phil

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=863E65DC-345E-47FF-8031-6CA897C451E9@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=beoram@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=phil@beadling.co.uk \
    /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.