Conversation

Notices

1. Vertigo (vertigo@mastodon.social)'s status on Tuesday, 04-Apr-2017 21:44:05 UTC Vertigo

   Yes, I'm thinking that the right steps forward for the Kestrel project is to definitely develop Forth for it, beyond the current eForth implementation, and then port Shen Lisp to run on top of Forth.

   Then, from there, build much of everything else I need. Low-level code uses Forth, high-level uses Lisp. [Alternate hard and soft layers](http://wiki.c2.com/?AlternateHardAndSoftLayers) to build the total stack. Best of both worlds.

   • Hallå Kitteh likes this.
   • Hallå Kitteh repeated this.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Wednesday, 05-Apr-2017 06:19:52 UTC Hallå Kitteh

     in reply to
     @vertigo Haven't heard about http://shenlanguage.org/ before, looks interesting!
     
     Do you know about #picolisp ?
   • Vertigo (vertigo@mastodon.social)'s status on Thursday, 06-Apr-2017 02:56:09 UTC Vertigo

     in reply to

     • Hallå Kitteh

     @clacke I've heard of it, but it doesn't look like it's nearly as easy to port as Shen. Shen is like Forth, in that it builds on top of a very small kernel of primitives and semantics. This appeals to me for its simplicity.

     Plus, it's optionally statically typed! This is wonderful news, since you can apply strong typing where it makes sense, and rely on dynamic typing everywhere else.

     Hallå Kitteh likes this.
     Hallå Kitteh repeated this.
   • Hallå Kitteh (clacke@social.heldscal.la)'s status on Thursday, 06-Apr-2017 07:19:41 UTC Hallå Kitteh

     in reply to

     • The Forth programming language
     @vertigo #picolisp is pretty !forth-like in a sense. Its a very small kernel, it bridges well with machine code and most of it is written in picolisp. But the kernel is in assembler and quite tied to the hardware. pico for x86-64 an x86 even have different features. I guess that makes it both easy and hard to port. Tiny kernel, but you need to rewrite it all each time.