Re:Programming Language Checklist
by cinnamonheart on Friday January 03, 2020 @10:18AM
(#21946566)
Have you heard of Unison? If not, it may interest you -- it stores code in a syntax tree rather than as text directly.
>Unison is a language in which programs are not text. That is, the source of truth for a program is not its textual representation as source code, but its structured representation as an abstract syntax tree.
It has some further goals for doing this which are really exciting to me, such as content-addressable code, but the starting point is similar to the one you stated. :)
Interesting indeed! Thanks for pointing this out.
Re:Programming Language Checklist
by stOneskull on Friday January 03, 2020 @11:30AM
(#21947374)
Interesting. And friendly..
Re:Programming Language Checklist
by Apanatshka on Friday January 03, 2020 @06:24AM
(#21944978)
Projectional editors use that setup. Might be slightly different than what you have in mind since projectional editing is not great at text editing. But have a look at Jetbrains MPS, that's a language workbench for projectional editors.
Re:Programming Language Checklist
by seanmcdirmid on Friday January 03, 2020 @08:17AM
(#21945561)
Simonyi’s Intentional programming also.
Re:Programming Language Checklist
by Traubenfuchs on Friday January 03, 2020 @12:00PM
(#21947721)
How about Java Bytecode?
You can write it in Java, Scala, Kotlin, Clojure, Ceylon, Groovy and many more.
This reminds me of "programming ligatures": https://github.com/tonsky/FiraCode
In SmallTalk you had everything as part of a binary "image". The compiler/interpreter, debugger, IDE, the standard library, your source and everything else was in one big blob.
This sounds like assembler.
That's waaaay to low level for what I had in mind.
Congratulations, you just invented AppleScript!
i feel it's more like LISP (the AST is the language) or like Haskell's or Rust's intermediary languages.
Re:Programming Language Checklist
by shadowgovt on Friday January 03, 2020 @10:29AM
(#21946669)
LISP coupled with an IDE that let you plug in higher-level abstract editors that represented their state as valid LISP code could almost fit the bill.
The editor plugin (in contrast to existing language plugins) also translates the error msgs back to the human-readable code.
Just an idea, but I could not get it to fit in the questionaire :)