From: Blake Shaw <blake@nonconstructivism.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: guix-days@gnu.org, guile-user@gnu.org, guix-user@gnu.org
Subject: Re: Proposal: Deep Dive into the Guile Docs & Makeover Proposal
Date: Sat, 19 Feb 2022 01:05:18 +0700 [thread overview]
Message-ID: <87bkz4xd7l.fsf@nonconstructivism.com> (raw)
Olivier Dion <olivier.dion@polymtl.ca> writes:
> On Thu, 17 Feb 2022, Blake Shaw <blake@nonconstructivism.com> wrote:
>
>> looking forward to any feedback.
>
> Some things that I think could use some improvement:
>
> When you play a video while you're talking, make sure that the
> volume of the video is very low so we can still hear you. For
> example, around 4.20 I can't hear you anymore (headphone). At
> least the music is good.
>
> There's time where you say Guix when you meant Guile or Scheme I
> think. For example around 13.40, you show a Git tree as a S-exp
> and refer to Guix.
>
> Looks like there's a latency between the audio and video. Maybe
> it's peertube and not your recorder.
>
> If you use the REPL again for a presentation that is presented
> live, I would suggest to add page number so that it's easier to ask
> questions and reference the good slide. In theory, one can use the
> $* variable of the REPL for that also.
>
noted! first screencast on Guix so a few issues I didn't anticipated,
I'll keep them in mind for next time.
> The very good points of your presentation I think are:
>
> Your language is impeccable and very cleared/articulated.
>
> I like that you show your real world usage of Guile. I feel that it's
> very important to show what Guile is capable of and that it can be
> used in a professional working environment.
>
> Overall, a great presentation.
>
thanks!
> For your `scribble jam` project, maybe you should look into
> guile-chickadee <https://dthompson.us/projects/chickadee.html>. It's a
> game development toolkit -- based on guile-opengl -- which I think
> support most of what you want. So you could use it in some way for your
> project.
>
yes, I've looked at it, but not deeply (this was a recently commissioned
work). I won't really be getting started on scribble jam for a few
weeks, but will poke at chickadee to see if it's suitable in the meantime.
> Other comments:
>
> For `Initialization with C` I would call it `C runtime initialization`.
>
> IMO, `Snarfing macro` should be in the same section as FFI.
>
> `Scheduling` -> `Multi-Threading` | `Parallelism`.
>
> `GOOPS` should be under `Guile Modules` or renamed to `Object
> Oriented Programming` like `Functionnal programming`.
>
> SXML is not just used in Web. So I'm not sure if it should be
> under the same section. Perhaps under parsing?
>
> `File Tree Walk` moved to `File System` and rename `POSIX/File System`
> to just `File System`.
>
> Best regards,
> old
thanks for the feedback and hope you join in tomorrow.
best,
blake
--
“In girum imus nocte et consumimur igni”
next reply other threads:[~2022-02-18 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 18:05 Blake Shaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-17 16:58 Proposal: Deep Dive into the Guile Docs & Makeover Proposal Blake Shaw
2022-02-18 17:48 ` Olivier Dion via General Guile related discussions
2022-02-19 12:17 ` Neil Jerram
2022-02-19 15:33 ` Olivier Dion via General Guile related discussions
2022-02-19 17:35 ` adriano
2022-02-16 22:06 Blake Shaw
2022-02-08 16:59 Blake Shaw
2022-02-08 17:28 ` Daniel Tornabene
2022-02-08 15:21 Blake Shaw
2022-02-08 13:06 Blake Shaw
2022-02-08 7:36 Blake Shaw
2022-02-08 9:07 ` Neil Jerram
2022-02-08 11:46 ` Blake Shaw
2022-02-08 15:22 ` Daniel Tornabene
2022-02-08 10:16 ` Jérémy Korwin-Zmijowski
2022-02-08 14:45 ` james
2022-02-08 15:08 ` Olivier Dion via General Guile related discussions
2022-02-08 17:25 ` Daniel Tornabene
2022-02-10 17:20 ` Christine Lemmer-Webber
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=87bkz4xd7l.fsf@nonconstructivism.com \
--to=blake@nonconstructivism.com \
--cc=guile-user@gnu.org \
--cc=guix-days@gnu.org \
--cc=guix-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).