radial and flon
These ports aren't part of the "I was copying too much" complaint I emitted above. I had simply noticed that I was porting flon one to one to Ruby and I felt uneasy about it as it progressed.
a radial core to flon
Looking back a flon itself, I was quite happy at the libraries I had built to support it. I was telling myself: so, I'm building an interpreter, all this difficult C will be hidden behind it and life will be good. I was thinking about the fun radial language I was stashing together for flon, a language strong at JSON.
I started to wonder: what if the flon business logic was written in radial itself?
I started prototyping a core radial interpreter and I named the project flar.
This core would be a minimal, non-concurrent radial interpreter, a core for flon and flor (Ruby flon). The non-core instructions, like "concurrence", "task" and the non-core attributes like "timeout", etc would be implemented as libraries (either radial, either C or Ruby depending on the target).
By non-core, I think workflow-esque stuff. The core language would be a limited yet funny programming language.
That's the plan. I try to devote one or two hours per day to it. It feels right for now.