unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: wolf <wolf@wolfsden.cz>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	help-guix <help-guix@gnu.org>
Subject: Re: VSCode DevContainer for Guix? (Yasuaki Kudo)
Date: Wed, 12 Jul 2023 10:27:03 +0200	[thread overview]
Message-ID: <ZK5j1_4qrfG27Dcn@ws> (raw)
In-Reply-To: <18CDB333-9287-43E3-8C74-37ED66B31750@yasuaki.com>

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

On 2023-07-12 10:22:33 +0900, Yasuaki Kudo wrote:
> Thank you for this link Zelphir!
> 
> While I don't know much about this, it smells like the restrictions are the same sort that Chrome and Firefox put as the proprietary surface layered on top of the respective copyleft foundation?
> 
> I tried the de-microsofted VSCodium when I used to run GuixOS (Now I am back to Ubuntu) but it didn't work well so I left it at that 😅
> 
> My gut feeling is that Guix will excel at as niche and very efficient software packaging system and the popularity and adoption could expand from there. 
> 
> So I thought VSCode DevContainer could be a very good place to start!  
> 
> An example use case I can think of is for GitHub Actions continuous integration.  It seems to me that local SSD caching (10GB) is almost instantaneous. We can cache the Guix build dependencies there.  
> 
> Then, it will create a Docker image as an artifact from the CI-run.  The image is as small as it can be because Guix only installs the necessary software.

Careful about this assumption, Guix-generated container images are pretty large
and include a lot of things you might not want in there (man, info pages, bash,
...).  I am not saying "do not use it", but if you try to convince people to use
Guix for container builds, size should not be your argument (especially since
Alpine exists as an alternative).

> 
> This will be very beneficial because the artifact (Docker images) uploads/downloads seem to very slow!
> 
> This way, we can gradually introduce Guix to development teams as niche software for specific cases?  (The guix docker images will work together with many other docker images created in conventional ways)
> 
> -Yasu
> 
> > On Jul 12, 2023, at 04:23, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> > 
> > Hello Yasu,
> > 
> > There are some legal aspects about using the official "marketplace" from other than the official VSCode build: https://github.com/VSCodium/vscodium/blob/master/DOCS.md#extensions--marketplace at least according to the VSCodium linking to https://github.com/microsoft/vscode/issues/31168, wherein someone interpreted things: https://github.com/microsoft/vscode/issues/31168#issuecomment-1136375670.
> > 
> > Not sure this plays any role in your proposed process. It is something to keep in mind.
> > 
> > Regards,
> > Zelphir
> > 
> >> On 7/11/23 18:00, help-guix-request@gnu.org wrote:
> >> Send Help-Guix mailing list submissions to
> >>    help-guix@gnu.org
> >> 
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >>    https://lists.gnu.org/mailman/listinfo/help-guix
> >> or, via email, send a message with subject or body 'help' to
> >>    help-guix-request@gnu.org
> >> 
> >> You can reach the person managing the list at
> >>    help-guix-owner@gnu.org
> >> 
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of Help-Guix digest..."
> >> 
> >> 
> >> Today's Topics:
> >> 
> >>    1. VSCode DevContainer for Guix? (Yasuaki Kudo)
> >> 
> >> 
> >> ----------------------------------------------------------------------
> >> 
> >> Message: 1
> >> Date: Tue, 11 Jul 2023 05:55:33 +0900
> >> From: Yasuaki Kudo <yasu@yasuaki.com>
> >> To: help-guix <help-guix@gnu.org>
> >> Subject: VSCode DevContainer for Guix?
> >> Message-ID: <BB9B5B1E-810C-4315-AD49-9FEC156F5E9E@yasuaki.com>
> >> Content-Type: text/plain; charset=utf-8
> >> 
> >> Hello!!
> >> 
> >> So I have just spent a month battling with Docker and VSCode for a project and became familiar with them.  Combining both, we can create a very pleasant and reproducible developer environment that everyone can copy.
> >> 
> >> DevContainer is like Screen/Tmux on steroids - the heavy lifting of compilation and running can be shifted to a Docker, a remote SSH session, or a combination of both, while the end-programmer can interact with the local VSCode IDE.  And the developer-facing computer can be any of the 3 - Linux, Windows or Macintosh (inclusive of Apple custom CPU)
> >> 
> >> A development team can share the exact same environment using this mechanism.
> >> 
> >> I think we should have such a DecContainer for Guix programmers? 😄
> >> 
> >> -Yasu
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> ------------------------------
> >> 
> >> Subject: Digest Footer
> >> 
> >> _______________________________________________
> >> Help-Guix mailing list
> >> Help-Guix@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/help-guix
> >> 
> >> 
> >> ------------------------------
> >> 
> >> End of Help-Guix Digest, Vol 92, Issue 9
> >> ****************************************
> > 
> > -- 
> > repositories: https://notabug.org/ZelphirKaltstahl
> > 
>

W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

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

  reply	other threads:[~2023-07-12  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.87.1689091255.20905.help-guix@gnu.org>
2023-07-11 19:23 ` VSCode DevContainer for Guix? (Yasuaki Kudo) Zelphir Kaltstahl
2023-07-12  1:22   ` Yasuaki Kudo
2023-07-12  8:27     ` wolf [this message]
2023-07-12 11:27       ` Ekaitz Zarraga
2023-07-12 23:50         ` Yasuaki Kudo
2023-08-23 15:12       ` 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

  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=ZK5j1_4qrfG27Dcn@ws \
    --to=wolf@wolfsden.cz \
    --cc=help-guix@gnu.org \
    --cc=yasu@yasuaki.com \
    --cc=zelphirkaltstahl@posteo.de \
    /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).