public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: David Pirotte <david@altosw.be>
Cc: kawa <kawa@sourceware.org>
Subject: Re: a Kawa wikipedia page would be cool...
Date: Sat, 28 Oct 2017 19:05:00 -0000	[thread overview]
Message-ID: <16884efd-24ca-0ad8-4c65-05645e97cc69@bothner.com> (raw)
In-Reply-To: <20171028155420.376ebafc@capac>

On 10/28/2017 10:54 AM, David Pirotte wrote:
> Hi Per,
> 
>> https://en.wikipedia.org/wiki/Kawa_(Scheme_implementation)
> 
> Ah, I did enter 'kawa' in the search box of the hy wikipedia page before to post
> here, and it does not list anything about Kawa_(Scheme_...). I just tried again
> using the search box of the kawa page, just to confirm, and same 'no match'
> 
> 	Maybe worth a word with the wikipedia folks...
> 
> I really don't like the 1st sentence, because it gives the impression it is for
> language implementors only, where as, imo, kawa is a scheme implementation, first
> and before anything else,  that allows programmers _not_ to have write java (the
> clojure 'slogan, nobody should never have to write java code...)

I vaguely remember there were two pages: 'Kawa (Scheme implementation)'
and 'Kawa (Language framework)' (or something like that).  Did someone try to merge
those two pages.

To me, as an implementor, Kawa isn't just a Scheme implementation.  There are
other languages implemented using the Kawa framework - some but not all included
with the Kawa source release.

However, for most people, Kawa is interesting an actual Scheme-variant programming language.
So perhaps the first paragraph should focus on that.  A second paragraph, maybe something like:

   The Kawa compiler tools can be used to implement other languages, some
   of which (such as an implementation for XQuery 1.0) are included in the Kawa distribution.

> The page should really be reviewed, to make it extremely attractive, and _the_
> language that one would want to use if they have to do anything in java ... it
> should also explains the advantages it has over clojure (start-up time and a so much
> better integration with the java class system ...
> 
> 	all this with real example, a real complete little app...
> 
> 	a 2D clock, as I wrote for guile-clutter might be a good example, and how one
> 	could run it in java, and android ... maybe :)
> 
> 		http://www.nongnu.org/grip/examples.html
> 
> Then it says
> 
> 	To run Kawa on GNU/Linux:
> 
> 		$ export CLASSPATH=$CLASSPATH:/path/to/kawa/kawa-1.10.jar
> 
> 	1.10 ? ...

I fixed that.

> 
> Voilà :) my 2c
> 
> 	Not me though, I'm totally over loaded with my GNU projects and rarely use
> 	kawa anyway (I do when I have to use imagej, precisely because I
> 	don't want to write in java...
> 
> 	One of the superior advantage of kawa to clojure is that we don't even need
> 	to interact with the java ecosystem, just kawa -C mycode.scm > mycode.Class
> 	then we can import and, you feel like you are in Guile, or Racket
> 
> All we need is emacs, and a repl, then geiser:
> 
> 	Per, any progress on dynamic (re)compilation? not a big deal, just
> 	curious

None so far.  I've been focused on DomTerm (http://domterm.org/) - adding
tmux/screen-style session management.  After that I think the priority
is moving the Language Server along for IDE support.  (Both of these have
synergies with the dynamic recompilation goal.)

> It is just that I am irritated to see clojure every where and never kawa, which is
> so much better ... so today I did my part and added this entry in the HY page :):)

Imagine how I feel ...

-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-10-28 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28 17:04 David Pirotte
2017-10-28 17:09 ` Per Bothner
2017-10-28 17:54   ` David Pirotte
2017-10-28 19:05     ` Per Bothner [this message]
2017-10-30  8:02       ` Damien Mattei

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=16884efd-24ca-0ad8-4c65-05645e97cc69@bothner.com \
    --to=per@bothner.com \
    --cc=david@altosw.be \
    --cc=kawa@sourceware.org \
    /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).