Advertisement
Advertisement
β‘ Community Insights
Discussion Sentiment
88% Positive
Analyzed from 294 words in the discussion.
Trending Topics
#bonsai#ocaml#backend#language#frontend#web#write#caml#need#frameworks
Discussion Sentiment
Analyzed from 294 words in the discussion.
Trending Topics
Discussion (14 Comments)Read Original on HackerNews
Finally! I was waiting for this to become possible!
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.
> JSOO does not have tail call optimization
Let me re-write that section for you:
Why Bonsai?
At Jane Street we're super excited by Functional programming and by CAML in particular, so when we need low latency software, we use OCAML, when we need hardware, we write out own langauge - HardCAML, and when we need a Web UI, we build a Web UI framework in CAML. Because we fucking love CAML.
Yea, its cool to have strict type safety, but what's the point of it doesn't have all the benefits from other Frameworks that took years to polish