Dark is a very cool project. I had the opportunity to consult with them and Paul is an extremely bright engineer. I agree with the premise of the problems they want to solve and hope they can get there.

It’s interesting to me though that a project that includes its own programming language has changed languages twice. (Elm to OCaml on the front end, OCaml to F# on the backend) and does kind of call out the fact that anything built on the dark platform is locked into Dark the language.

Dark has shown that changing languages can provide benefits like the ones quoted in the blog, so maybe it would be worth exploring more language support. Reading past comments and feedback, it seems like embracing a whole new language was a high barrier to entry for most.

I’d really like to understand more of this. Any chance you could make an Ellie or something to demonstrate?

I don't have one on Ellie, but Ellie itself has a nice example with how it wraps CodeMirror (https://github.com/ellie-app/ellie/blob/master/assets/src/El...)

I don't know if there is a formal name for this pattern, but we've been calling in the "un-attr" pattern, you define an opaque type like

  type Attribute msg
      = Attr (Html.Attribute msg)

And then expose functions that allow you to set attributes you whitelist. In the JS you use setters to hook into when the attribute changes and respond to it (https://github.com/ellie-app/ellie/blob/master/assets/src/El...)