Re: [MirageOS-devel] Blog post on Irmin/CueKeeper

[Drup <drupyog+caml@xxxxxxxx>]

> Finally got around to writing this up:
>
> http://roscidus.com/blog/blog/2015/06/22/cuekeeper-internals-irmin/
>
> I'd be particularly interested to hear about suggestions for avoiding
> the React GC issues.
Very nice write up! I was eagerly waiting for it; especially the 
tyxml/react part, since we didn't got much feedback on that. I'm rather 
happy to see that you used it and enjoyed the convenient combinators and 
the additional type safety. I agree that the documentation is less than 
satisfactory, I have yet to find a nice way to document such complex 
typing.
I'm surprised you understand it by *reading the code* given the 
functorization and the typing. :D
Apart from the typical react issues, what was your feeling on the tyxml 
react things, from a GUI building aspect ?
For the GC issues, Lwt_react[1] helps a bit, in particular E.keep and 
S.keep. It basically implements your "global sink" idea. Doesn't solve 
the space leaks in javascript, though. Lwt_react in general is a very 
nice improvement over React when used in conjunction with Lwt.
You didn't seem to use Lwt_js_events (or just didn't talked about it) in 
jsoo, is there a reason ?
Otherwise, the contribution of the indexedDB api to jsoo's api would be 
very welcome. ;)
The bigstring and bin_prot primitives have been implemented in js now 
(part of hhugo's effort to make Async work on jsoo), so you shouldn't 
need them any more.
[1]: http://ocsigen.org/lwt/2.4.8/api/Lwt_react



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel