nqp VS enso

hi! I was looking at REPL-like evaluation of code from here and here, and tried to make a very small version for it, yet it fails:

Second, any "inheritance" is optional. Quoting nqp's 6model overview with my added emphasis:

Considering it has a compiler (which generates an NFA), I do not think it is fair to call it an interpreter.

When I mention the Actor model, I specifically mean the Actor model, not "an actor model". That is to say, a mathematical theory, not an implementation. In contrast, ponder what you mean by "an object model". When I mention the "metamodel", I specifically mean "a framework [that] does not contain an implementation of classes, interfaces, roles, prototype objects and so forth".

NQP is a compiler like MiniPerl for Perl 5. It is a bootstrapping tool which helps to compile the Raku parts of Rakudo and compile the libraries before running have compiled the libraries. Unlike MiniPerl for Perl 5 (which is an interpreter that can interpret all Perl syntax but miss some batteries: means without modules mixing Perl code and native code), NQP can only compile a "simplified Raku". NQP refers to both the compiler and the source code contained in files with the ".nqp" extension.

I focus on the Raku stack: the compiler Rakudo which targets the compiler compiler NQP which targets multiple backends including MoarVM. (Which

NQP is a compiler compiler toolkit that targets multiple backends: JVM, JS, and MoarVM.

> At least I have yet to see one that is actually useful in the sense of a generic (or even a single-purpose-built) language

Yeah as said, https://github.com/enso-org/enso seems to be a general purpose functional programming language with visual editor, but otherwise I haven't really seen any no-code solutions worth their salt. I'm not particularly a fan of enso either, but it's the best I've seen.

Although it's not quite the same, I do like what Enso[0] is bringing to the table, especially the 1:1 visual node/language interop. Whether this is generalisable to a fully decoupled interface remains to be seen, but there's definitely potential.

[0]: https://enso.org/

I think Enso is already taken by a YC company [0]. Could get confusing.

[0] https://enso.org

COMPANY: Enso Inc. TYPE: Full time LOCATION: Europe and United States of America – fully distributed company REMOTE: Only remote VISA: No VISA required DESCRIPTION: Hi, we are Enso (enso.org, Y Combinator S21)! We are looking for an amazing Cloud engineer to join our core team. We are a remote first company, working in Europe and the USA.

Friends of mine are developing Enso (https://enso.org/), an interactive programming language with dual visual and textual representations.

Even well before Bret Victor's time, there were tools for visual programming. I have been using LabView to maintain data processing in an optical laboratory.

> I'm convinced this entire space should be visual.

At my last 2 jobs I spent entirely too much time debugging Matillion jobs, which are visual. I have my doubts that it’s the panacea that it appears to be.

That said, you may find Enso particularly interesting: https://github.com/enso-org/enso