From: bokr@bokr.com
To: Maxime Devos <maximedevos@telenet.be>
Cc: Blake Shaw <blake@sweatshoppe.org>,
Luis Felipe <luis.felipe.la@protonmail.com>,
guile-user@gnu.org, Guix Devel <guix-devel@gnu.org>
Subject: Re: Wiki && Re: [feature request] merge sxml->html from (haunt html) into guile?
Date: Wed, 29 Jun 2022 05:26:41 +0200 [thread overview]
Message-ID: <20220629032641.GA5817@LionPure> (raw)
In-Reply-To: <a9e203b96f504bed5e3ab99ad5173aedbb04ec95.camel@telenet.be>
On +2022-06-28 22:13:58 +0200, Maxime Devos wrote:
> Blake Shaw schreef op wo 29-06-2022 om 01:34 [+0700]:
> > Which brings up another thing I've been considering working on thats
> > been discussed in the Guix community: the need for click-to-edit
> > wiki, written in Guile. [...]
>
> I don't think ‘written in Guile’ has been discussed?
>
> Also, I don't see the point in writing our own wiki software in Guile
> when there's already plenty of Wiki software in existence with lots of
> tools for moderation, version control, backups, lots of testing, etc.
> Why not reuse pre-existing work instead of reinventing the wheel (likely
> poorly, at least at first)?
>
E.g.? :
https://docs.racket-lang.org/web-server/index.html
Not guile, but close in the family tree :)
(I don't know how good their server stuff is, but
I get the impression they consider it production quality)
> Greetings,
> Maxime.
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2022-06-29 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 6:57 [feature request] merge sxml->html from (haunt html) into guile? Blake Shaw
2022-06-28 13:26 ` Luis Felipe
2022-06-28 18:34 ` Wiki && " Blake Shaw
2022-06-28 20:13 ` Maxime Devos
2022-06-28 21:05 ` Maxime Devos
2022-06-29 3:26 ` bokr [this message]
2022-06-29 6:19 ` Dr. Arne Babenhauserheide
-- strict thread matches above, loose matches on Subject: below --
2022-06-28 19:57 dsmich
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=20220629032641.GA5817@LionPure \
--to=bokr@bokr.com \
--cc=blake@sweatshoppe.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=maximedevos@telenet.be \
/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).