Re:Compile OCaml to JavaScript, Run on Node
by Drup on Thursday December 03, 2015 @03:26PM
(#10672330)
As someone working on eliom, I would really like to hear you on the areas where we can improve seamless-ness. :)
[ Parent
| on HN ]
Re:Compile OCaml to JavaScript, Run on Node
by murbard2 on Thursday December 03, 2015 @09:19PM
(#10674168)
To be honest, I haven't used it seriously enough to give you the good answer this deserves.
A friend of mine evaluated it for his own need and went with Meteor citing that reason (plus ease of hiring for js). I've gotten a similar feel looking at the code samples.
Take for example this basic example:
{server{
let get_data_forum forumid =
lwt messages = Db.get_messages forumid in
let default = {'a option{
try Some (Eliom_cscache.find_if_ready %forumcache %forumid)
with _ -> None
}}
in
Lwt.return (SharedReactiveData.RList.make ~default messages)
let get_data_forum_rpc =
server_function Json.t<int>
(Eba_session.Opt.connected_rpc
(fun userid_o forumid -> get_data_forum forumid))
}}
{client{
let get_data_forum forumid = %get_data_forum_rpc forumid
}}
This feels awfully verbose for what it does...