unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Phil <phil@beadling.co.uk>
To: Benjamin Slade <beoram@gmail.com>
Cc: Yasuaki Kudo <yasu@yasuaki.com>,
	Olivier Dion <olivier.dion@polymtl.ca>,
	help-guix@gnu.org
Subject: Re: Enterprise Guix Hosting?
Date: Sun, 31 Jul 2022 12:01:09 +0100	[thread overview]
Message-ID: <87bkt5a6mi.fsf@beadling.co.uk> (raw)
In-Reply-To: <0c1f853a-f613-4ad2-9eda-05940cee5a23@gmail.com>


Benjamin Slade writes:

> Not something I've tried personally, but maybe PantherX (Guix-based) could be relevant here? https://www.pantherx.org/

This is very interesting - there is definately a niche to produce
off-the-shelf guix-based enterprise solutions that a mainstream devops
team could rollout and interface with "standard" tech tooling without
having to learn (a lot of) Scheme.

My own experience is that whilst it doesn't require a PhD to setup Guix
for the enterprise, it is a non-trivial journey, and it does require
a fair amount of time and effort to create something that regular
developers/scientists (i.e. non-Guix converts who just want to get on with their
day-jobs) accept is as good or better than regular tooling they are used
to.  There's certainly a barrier to entry for people who don't want to
do a deep-dive and just want tooling to support them in their professional
role, without them having to think about it too much.

Upselling the real benefits of Guix like rollbacks, profiles, perfectly
reproducable builds, swapping one dependency for another - even in a
scientific/tech-savvy company with lots of PhDs took a bit of persuading
from me. Even now I think our company is only using perhaps 30% of the
true power of Guix.  Making all that power accessible to people who just
want to get on with their jobs in an easy, intuitive way is a challenge
I'm continuously trying to address.  I also hope things like PantherX
might help bridge the gap in the near future! 


  reply	other threads:[~2022-07-31 11:01 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 [this message]
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
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

  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=87bkt5a6mi.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --cc=beoram@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=yasu@yasuaki.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.
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).