4 ms·
Seems like a bad thing? Why are there two separate workstreams?
by omginternets 3y ago
Seems like a bad thing? Why are there two separate workstreams?
- frou_dh 3y agoMaybe adapting the existing js_of_ocaml project is comparatively easier so they might as well try it.
- lambda_foo 3y agoThere is a pretty complete wasm_of_ocaml port to the Eliom web framework here https://github.com/ocsigen/eliom/pull/767 https://github.com/ocsigen/eliom/pull/767 It seems like it’s a relatively easy swap from js_of_ocaml to WASM. That’s the option I’ve chosen for my experiments.
- giraffe_lady 3y agoIt's the ocaml way.
- lambda_foo 3y agoThey are targeting two different intermediate representations in the compiler. wasm_of_ocaml is a fork of js_of_ocaml that consumes OCaml bytecode and emits Wasm instead of JavaScript. Compared to wasocaml that uses the FLambda-based backend for OCaml’s native code compiler. Time will tell if both survive, they are both under active development. IMHO target different use cases.