I am sure it's very performant, but to me it's extremely ugly; Surely someone can fix margins and still have it be performant.
I’m no UI expert - what’s wrong with the margins?
Bonsai: Janestreet's UI Library
31–40 of 165 posts
Re: Bonsai: Janestreet's UI Library
#32> 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!
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.
Yup, and Clojure/ClojureScript!
Re: Bonsai: Janestreet's UI Library
#33I am sure it's very performant, but to me it's extremely ugly; Surely someone can fix margins and still have it be performant.
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
Re: Bonsai: Janestreet's UI Library
#34This is great. It focuses on utility and information density over design. It looks like someone took a terminal UI and transplanted it to the web, Bloomberg terminal style.
I'm pretty sure you can build tools with this that are fast and pleasant to use.
Re: Bonsai: Janestreet's UI Library
#35Can 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?
Probably not, because your agent won’t have much info about this tool in its training set.
Re: Bonsai: Janestreet's UI Library
#36Why does this library get posted here, what feels like every month? I remember it seeing at least twice before.
Been here 5 years, never saw it
Re: Bonsai: Janestreet's UI Library
#37Re: Bonsai: Janestreet's UI Library
#38Earlier 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.
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.
Re: Bonsai: Janestreet's UI Library
#39> 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.
Re: Bonsai: Janestreet's UI Library
#40Earlier 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
From experience I can say that traders prefer extraordinarily little whitespace in their UIs.