unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Newbie thoughts on Guile Hall + Guix
Date: Wed, 9 Feb 2022 12:05:13 -0800	[thread overview]
Message-ID: <CA+XASoUz5rU4nr6474jW++NcJCgYWCeROP5p+vXwoF0kDJwwXQ@mail.gmail.com> (raw)
In-Reply-To: <87bkzg5dr6.fsf@laura>

My 2 cents:

- Doing something in Guile is tough. I've been trying since 2011.

Why is it tough?

- The manual is written by very smart people for very smart people. Not for
newcomers. I'm excited to see what Blake comes up with, but the content
will probably still be not-trivial. At the end of the day it's a reference
manual, not a book to teach you how to write a new project from scratch.

- There are no simple and modern resources that teach what is the
"Guile/Scheme" way. How do you even organize a project when you start? Or
something like https://go.dev/tour/ to teach the basics. Yes, you can read
books but most people when they start to learn a new language they just
want to try to do something quick. And the books that teach Scheme are not
trivial/practical.

- Lack of libraries. We do have libraries but the ecosystem is not big and
for those libraries we have it's hard to get started, most don't have
simple examples or don't have examples at all.

- Assuming you find the library you need... how do you start using it? How
do you install it? Now there's Guix, but not everyone has Guix or wants to
install Guix. I'm on macOS currently so I can't even install Guix
unfortunately.

- Lack of support in editors other than Emacs (yes, geiser is great!).
There's a project that might help there:
https://gitlab.com/rgherdt/scheme-lsp-server. But LSP is not enough, you
need a paredit equivalent, etc.

- Creating a new library is (or was) not easy. guile-hall and guix help
here. But how do newcomers even find "guile-hall"? Should guile-hall be
part of Guile and included in the manual?

- Distributing the new library you have created is (or was) not easy
either. Also, guile-hall and guix issues here.

So basically today we are kind of forcing people to learn Emacs and Guix
(if you can even use Guix) to have a minimum decent environment.

For me starting with Guile was not hard because of autotools, I already had
to deal with that for many years. For me the hardest part was the lack of
resources (libraries, tutorials, examples, simple books).

As for myself, I've been trying to create libraries to replicate what I use
at work (and I'm far from that) or others that I find fun. And I will try
to keep doing that to improve Guile's ecosystem and help with anything else
I can.

Best,

Aleix


  reply	other threads:[~2022-02-09 20:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 10:30 Newbie thoughts on Guile Hall + Guix Blake Shaw
2022-02-09 14:13 ` Olivier Dion via General Guile related discussions
2022-02-09 20:05   ` Aleix Conchillo Flaqué [this message]
2022-02-09 20:28     ` Maxime Devos
2022-02-09 21:13       ` Aleix Conchillo Flaqué
2022-02-10 18:03     ` Vivien
  -- strict thread matches above, loose matches on Subject: below --
2022-02-10 12:42 Blake Shaw
2022-02-09  3:23 Blake Shaw
2022-02-08 16:13 Blake Shaw
2022-02-08 12:19 Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09  6:28 ` Catonano
2022-02-06 13:40 dsmich
2022-02-05 20:01 Christine Lemmer-Webber
2022-02-05 22:15 ` Mikael Djurfeldt
2022-02-05 23:19   ` Jose Antonio Ortega Ruiz
2022-02-06 14:09     ` Ricardo Wurmus
2022-02-06  0:40   ` Christine Lemmer-Webber
2022-02-06  4:54     ` Aleix Conchillo Flaqué
2022-02-06 13:14       ` Mikael Djurfeldt
2022-02-06 14:03         ` Ricardo Wurmus
2022-02-06 14:28           ` Vijay Marupudi
2022-02-06 14:53             ` Ognen Duzlevski
2022-02-06 15:13               ` Maxime Devos
2022-02-06 15:29               ` Vijay Marupudi
2022-02-06 21:34                 ` Zelphir Kaltstahl
2022-02-07  2:11                   ` David Pirotte
2022-02-07  2:47                     ` David Pirotte
2022-02-07 19:21                     ` Zelphir Kaltstahl
2022-02-07 22:35                   ` adriano
2022-02-05 22:16 ` Vivien
2022-02-06  2:53 ` Zelphir Kaltstahl
2022-02-06 16:35 ` Olivier Dion via General Guile related discussions
2022-02-06 16:44   ` Vivien Kraus
2022-02-06 22:10     ` Olivier Dion via General Guile related discussions
2022-02-06 16:55   ` Maxime Devos
2022-02-06 22:05     ` Olivier Dion via General Guile related discussions
2022-02-06 22:32       ` Maxime Devos
2022-02-06 23:00         ` Olivier Dion via General Guile related discussions
2022-02-06 21:37   ` Zelphir Kaltstahl
2022-02-06 22:12     ` Olivier Dion via General Guile related discussions

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+XASoUz5rU4nr6474jW++NcJCgYWCeROP5p+vXwoF0kDJwwXQ@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).