We need to organize what backends we want and how we're going to build them. - [x] **LLVM**: As the most optimized backend, LLVM is great for speed, but can be bad for compile times. - [x] **JVM**: ASM will probably be the library we use. - [ ] [**Parrot**](http://www.parrot.org/): Parrot's IR is very simple but doesn't have complex types. - [ ] [**NekoVM**](http://nekovm.org/): Neko should be easy to compile to. - [ ] **WASM/JS**: Putting the language on the web will be cool, and WASM gives us the static typing and speed we want. - [ ] [**B3**](https://webkit.org/docs/b3/): Webkit's new backend seems promising, and using JavaCPP will make it easy to call. - [ ] [**Cretonne**](https://github.com/stoklund/cretonne): A Rust backend might be hard to call. - [ ] [**MoarVM**](http://moarvm.com/)
We need to organize what backends we want and how we're going to build them.
LLVM: As the most optimized backend, LLVM is great for speed, but can be bad for compile times.
JVM: ASM will probably be the library we use.
Parrot: Parrot's IR is very simple but doesn't have complex types.
NekoVM: Neko should be easy to compile to.
WASM/JS: Putting the language on the web will be cool, and WASM gives us the static typing and speed we want.
B3: Webkit's new backend seems promising, and using JavaCPP will make it easy to call.
Cretonne: A Rust backend might be hard to call.
MoarVM