Similar attempts include Scalajs.

The general challenge becomes integrating the fractional front-end code written in your backend-language that compiles to JS with the rest of the JS ecosystem.

JaneStreet have a love of writing their own stuff from scratch so it doesn't apply to them but it might to you.

Hence most people end up with frontend-as-backend rather than backend-as-frontend.

▲

raphinou 2 hours ago | parent | next [-]

Such attempts are quite common. Some I remember:

https://ocsigen.org/ in Ocaml too

https://websharper.com/ for fsharp and csharp. Really good when I used in in fsharp

Maybe https://melange.re/v7.0.1/ too? (Not sure)

▲

vintermann an hour ago | parent [-]

I took this as a joke in reference to the popularity of JavaScript on the backend for the last two decades.

	▲	reactordev 36 minutes ago \| parent [-]
		that's because most people's intro to CS was how to build a webpage.

▲

nobleach an hour ago | parent | prev | next [-]

Yup, and Clojure/ClojureScript!

▲

lbourdages 2 hours ago | parent | prev [-]

Couldn't WASM solve that problem once and for all? Is there some limitation that WASM has that JS doesn't?

Disclaimer: I am very inexperienced at front-end development.

	▲	danielheath 2 hours ago \| parent \| next [-]
		> Is there some limitation that WASM has that JS doesn't? You need a JS trampoline to call your WASM and make browser primitives available to it, and IIRC calls into browser code incur some extra overhead, but those are pretty manageable. Additionally: for high level languages, source code is _much_ smaller than compiled binaries. If your initial needs are simple, your users are likely downloading more than 10x as much code.
	▲	applfanboysbgon 8 minutes ago \| parent \| prev [-]
		WASM does not (yet) have access to the DOM or web APIs, meaning every direct interaction with the browser must first go through JS interop anyways, with a resulting performance penalty. There are proposals, and maybe we'll see it happen by 2035, but as of now WASM is best suited for heavier workloads where the edge in application performance outweighs the cost of JS interop with the browser rather than being a universal solution.