My kingdom for a modern implementation of ocaml-java πππ #ocaml
=> More informations about this toot | More toots from cemerick@mastodon.social
This is bad. I did a little poking around, and a js_of_ocaml-style approach to an OCaml-for-java looks "easy" enough I might start picking at it in my ample free time.
Help.
=> More informations about this toot | More toots from cemerick@mastodon.social
@cemerick Did we just witness a self-nerd-snipe? Oooh-those-are-rare.jif !!
=> More informations about this toot | More toots from pmonks@sfba.social
@pmonks I have a really bad reputation for that kind of thing.
=> More informations about this toot | More toots from cemerick@mastodon.social
@cemerick Donβt we allβ¦ sigh
=> More informations about this toot | More toots from pmonks@sfba.social
@cemerick how much of the jsoo bytecode transformation code is reusable in your opinion?
Would love to yakshave a back-end for Lua and Python.
=> More informations about this toot | More toots from nickmain@mas.to
@nickmain on first blush, probably not much. The general approach is what I'm optimistic about. tbc, it's not like I've done a deep dive on jsoo's implementation -- maybe there's some common bits that one could corral off to one side and build backend(s) for each target you're interested in, but that's feeling like a long shot given what I've learned so far.
=> More informations about this toot | More toots from cemerick@mastodon.social
@cemerick jsoo recently merged the wasm backend, so JVM bytecode backend when? π
=> More informations about this toot | More toots from leonidas@mastodon.social
@leonidas Just today I've opened a dozen tabs re: running wasm stuffs on the jvm and .net, yet to be read. If that's workable, then there's nothing to do
(Write once run anywhere, right? Right?! π)
=> More informations about this toot | More toots from cemerick@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini