41–50 of 165 posts
> And because Bonsai is written in OCaml, it becomes possible to use the same language and types on both the backend and frontend. Finally! I was waiting for this to become possible!
There's also Fable for F# but I believe this commenter is being sarcastic. Javascript is a common backend language.
Earlier quoted context omitted.
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)
I took this as a joke in reference to the popularity of JavaScript on the backend for the last two decades.
Can someone who understands web UI programming tell me if this would be good for my local agent to use to produce HTML based reports and outputs for me? Or for TUI outputs?
Earlier quoted context omitted.
I’m no UI expert - what’s wrong with the margins?
inconsistent and maybe too tight, but I would think those are issues with the sample UIs and not this library
They have dedicated UX designers who do relatively little code but focus entirely on making the UX as optimal for the traders as possible and one of them was on an episode.
They talked about how most of the normal UX rules for SW go out the window because quants and traders have such different needs than "normal software".
Thanks, I can use JS as a functional programming language.
Earlier quoted context omitted.
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.
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.
Earlier quoted context omitted.
I’m no UI expert - what’s wrong with the margins?
inconsistent and maybe too tight, but I would think those are issues with the sample UIs and not this library
We are at a point when TUIs from 1990s running in 12" screens with at best a 480x240 resolution display more info than almost anything we have now.
Earlier quoted context omitted.
inconsistent and maybe too tight, but I would think those are issues with the sample UIs and not this library
FWIW if you listen to Signals and Threads (the Jane Street podcast) they talk about this. They have dedicated UX designers who do relatively little code but focus entirely on making the UX as optimal for the traders as possible and one of them was on an episode. They talked about how most of the normal UX rules for SW go out the window because quants and traders have such different needs than "normal software".