3 Dominant Themes in the Bonsai Discussion
| Theme | Summary | Supporting Quote |
|---|---|---|
| 1️⃣ Functional UI written in OCaml, sharing code between front‑ and back‑end | Several users highlight that Bonsai lets you stay in a single language (OCaml) for both UI and server logic, removing the usual JS/TS bridge. | "There's a full terminal implementation of Bonsai as well. I actually use it in my personal workflow..." – avsm "Finally! I was waiting for this to become possible!" – philipwhiuk |
| 2️⃣ Practical concerns & ecosystem trade‑offs | Commenters raise questions about compile speed, maintainability, AI‑assisted development, and how Bonsai fits (or doesn’t) into existing JS/TS ecosystems. | "But what about compilation speed? Hot reload? Maintainability? What is the bus factor for these kind of technologies?" – rmzs0711 "Seconding the sibling comment – what are you using to run your personal site? It is very nice." – abtinf |
| 3️⃣ UI design philosophy – high information density for power users | A recurring thread is the preference for compact, data‑dense interfaces (especially for traders) rather than the “pretty” UI conventions of mainstream web apps. | "Traders prefer extraordinarily little whitespace in their UIs." – pgwhalen "Margins on an info dashboard are wasted space." – stronglikedan |
These three themes capture the enthusiasm for a unified OCaml UI stack, the pragmatic debates around its adoption, and the distinct design expectations of specialized, high‑density interfaces.