unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Joshua Branson <jbranso@fastmail.com>
Cc: guile-user@gnu.org
Subject: Re: How to get started in guile & programming generally
Date: Mon, 27 Aug 2018 22:54:15 +0200	[thread overview]
Message-ID: <87lg8ra5vo.fsf@web.de> (raw)
In-Reply-To: <87mut9uh6x.fsf@fastmail.com>

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


Joshua Branson <jbranso@fastmail.com> writes:

> Amirouche Boubekki <amirouche@hypermove.net> writes:
>>> Is there a programming resource for
>>> userspace/kernel software
>>
>> what do you mean by kernel software?
>
> My short term goal right now is to be able to write GNU/Hurd translators
> in guile.  My long term goal is to be a GNU/Hurd developer.

That’s cool! Several years ago I worked on the Pythong bindings for
translators (though I did not get as far as I’d have liked) and it’s
great to see paths converge again!

The common lisp bindings had some pretty nifty tools, so you might find
inspiration there. You can make a lot of difference with relatively
little effort.

One aspect in which where developing Guile is much more enjoyable than
programming in Python is that once you get used to using the info
documentation (i.e. via Emacs) you can work without googling, and a
full-text search in structured, relevant information beats a Google
search — even if Google leads you to Stackoverflow.

(for all those unfamiliar with the Hurd: Here’s a writeup about the
technical advantages of the Hurd:
https://www.draketo.de/light/english/free-software/some-technical-advantages-of-the-hurd )

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken

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

  parent reply	other threads:[~2018-08-27 20:54 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 17:16 How to get started in guile & programming generally Joshua Branson
2018-08-25 19:01 ` Amirouche Boubekki
2018-08-25 20:10   ` Pierre Neidhardt
2018-08-25 20:35     ` Matt Wette
2018-08-27 12:39     ` Ludovic Courtès
2018-08-27 13:15       ` Thompson, David
2018-08-26 18:16   ` Joshua Branson
2018-08-26 19:12     ` Pierre Neidhardt
2018-08-27 13:30       ` Thompson, David
2018-08-27 20:42         ` Arne Babenhauserheide
2018-08-29 21:21         ` Joshua Branson
2018-08-29 21:20       ` Joshua Branson
2018-08-29 21:27         ` Amirouche Boubekki
2018-08-30 13:11           ` Joshua Branson
2018-08-30 15:45             ` Amirouche Boubekki
2018-09-03 20:53           ` Joshua Branson
2018-10-19 17:02             ` Joshua Branson
2018-08-30 19:09         ` Arne Babenhauserheide
2018-08-31 11:32       ` Jan Nieuwenhuizen
2018-08-31 15:04         ` Thompson, David
2018-08-31 16:49           ` Jan Nieuwenhuizen
2018-08-31 23:04             ` Ludovic Courtès
2018-08-31 17:45         ` Amirouche Boubekki
2018-08-27 18:46     ` Amirouche Boubekki
2018-08-27 19:08       ` John Cowan
2018-08-29 21:33       ` Joshua Branson
2018-08-30 21:42         ` Arne Babenhauserheide
2018-08-31  8:07           ` tomas
2018-08-31 14:44             ` Joshua Branson
2018-09-01 10:00             ` Arne Babenhauserheide
2018-09-01 10:49               ` tomas
2018-09-02 23:09                 ` Arne Babenhauserheide
2018-08-31 14:42           ` Joshua Branson
2018-08-27 20:54     ` Arne Babenhauserheide [this message]
2018-08-29 21:35       ` Joshua Branson
2018-08-30 20:19         ` Arne Babenhauserheide
2018-08-31 14:41           ` Joshua Branson
2018-09-01 10:01             ` Arne Babenhauserheide
2018-09-01 16:26               ` Joshua Branson

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=87lg8ra5vo.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-user@gnu.org \
    --cc=jbranso@fastmail.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).