9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: Alexander.Shendi@web.de, 9front@9front.org
Subject: Re: [9front] Noob questions
Date: Fri, 19 Jun 2020 13:08:56 -0700	[thread overview]
Message-ID: <8AE0835E22EDF04A0A22B5188B85F5C5@eigenstate.org> (raw)
In-Reply-To: <BBDC2DA9-397B-4B30-8374-2DEA7A8F72C4@web.de>

> Hi,
> 
> Upon a whim I have installed the latest release of 9front (PLAN9-HATERS).
> 
> I have a few noob questions:
> 
> 1. I have "ported" EuScheme (a EuLisp Level 0 interpreter) and xlispstat ( a
> Sunset of Common Lisp with Extensions for statistical computing. Both based
> more or less on David M. Betz' XLISP. I have put ported in quotes because I
> have compiled using APE (ape/psh ape/make and ape/pcc). The compilation
> result runs under 9front w/o APE. It works so far for me. What should I do?

First, a quick nitpick: APE is really two different things -- it's a set of libraries that
emulate posix on plan 9, and a command line environment (both programs and namespaces) that
emulate a unix shell. Your program still uses ape, just not the shell part of it.

Using APE is an actual port. :)

> a. Use the stuff for my own purposes and keep quiet.

Make it available somewhere (sourcehut is nice this time of year, but any git
provider should work well enough.)

> b. Work on a "proper" port using 8c/6c and mk. Make the plot routines work using graph(1).

Depending on what you want from the port, and what kind of maintenance burden
you want to take on, this may or may not make sense.

The balancing act here is deciding how far to diverge from upstream to integrate
nicely into the environment, vs how much pain you're willing to tolerate keeping
up with upstream.

I usually encorage porters to try to keep the delta with upstream as small as
possible, and send the portability fixes that make sense upstream.

> c. Shut up, Install Linux or Windows and leave 9front and its users alone.
> 
> 2. I would like to have a array programming language at my disposal. Currently the most promising candidate is Rob Pike's Ivy. As it is written in Go, the way forward is:
> 2.1 Install a binary package of Go 1.4.3 or 1.14 (done).
> 2.2 Bootstrap a version of Go that is aber to compile Ivy from it using the pacjages from step 2.1.
> 
> Has anyone else attempted this? I would be grateful for any hints or recomendations.

Yep. It works pretty well.

There's even a ports repository that may help: http://code.9front.org/hg/ports/ 
Note, it's a lot jankier than I'd like, and could use a rewrite.



      parent reply	other threads:[~2020-06-19 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 18:56 Alexander Shendi (Web.DE)
2020-06-19 19:01 ` [9front] " Sigrid Solveig Haflínudóttir
2020-06-19 20:40   ` Alexander Shendi (Web.DE)
2020-06-19 20:56     ` Stanley Lieber
2020-06-19 20:03 ` Kurt H Maier
2020-06-19 20:08 ` ori [this message]

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

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

  git send-email \
    --in-reply-to=8AE0835E22EDF04A0A22B5188B85F5C5@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=Alexander.Shendi@web.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 NNTP newsgroup(s).