The idea of making DSL trivial to make is interesting, but my concern is that DSLs will become too easy to make. With DSLs falling on top of each other, suddenly you have a reasonable approximation of natural language, and the ambiguity of it. Now, one of the problems you have to reason about is how to make DSLs which can be composed in a way that they still read “articulately” and yet are still easy to use. I feel like the cognitive overhead would be overwhelming, although it could just be because I’m so unused to writing software in a natural-language-ish style.
One thing I thought was interesting was that they eventually jumped ship to the JVM. I like the idea of these heavily optimized runtimes being targets–there’s the LLVM, the CLR, and the JVM now, maybe the Go VM will eventually become a competitor if google continues to pour money into it? I wonder if writing a runtime will become the new version of “I’m writing a programming language in my spare time”
If you go up to a high enough level, you could make the argument that the Go runtime is it’s “VM.” Of course, you can make a lot of arguments if go up to a high enough level, but in this case I understood that when @moses said “VM,” he was referring to the “runtime.”
This is like the lord of the rings crossed with AppleScript? DwarfCard?
The idea of making DSL trivial to make is interesting, but my concern is that DSLs will become too easy to make. With DSLs falling on top of each other, suddenly you have a reasonable approximation of natural language, and the ambiguity of it. Now, one of the problems you have to reason about is how to make DSLs which can be composed in a way that they still read “articulately” and yet are still easy to use. I feel like the cognitive overhead would be overwhelming, although it could just be because I’m so unused to writing software in a natural-language-ish style.
One thing I thought was interesting was that they eventually jumped ship to the JVM. I like the idea of these heavily optimized runtimes being targets–there’s the LLVM, the CLR, and the JVM now, maybe the Go VM will eventually become a competitor if google continues to pour money into it? I wonder if writing a runtime will become the new version of “I’m writing a programming language in my spare time”
Go doesn’t have a VM. It compiles directly to native code.
If you go up to a high enough level, you could make the argument that the Go runtime is it’s “VM.” Of course, you can make a lot of arguments if go up to a high enough level, but in this case I understood that when @moses said “VM,” he was referring to the “runtime.”
I stand corrected. @untothebreach was right, I conflated runtime and VM.