[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On 22 Jun 2015, at 12:11, Thomas Leonard <talex5@xxxxxxxxx> wrote:
> On 28 April 2015 at 12:04, Thomas Leonard <talex5@xxxxxxxxx> wrote:
>> Although not finished, I thought CueKeeper was mature enough for a 0.1
>> alpha release and blog post:
>> http://roscidus.com/blog/blog/2015/04/28/cuekeeper-gitting-things-done-in-the-browser/
>> There's not much technical detail here because after adding some
>> instructions on how to use it, the blog was getting rather long, but
>> there is a section at the end demoing various nice benefits from using
>> Irmin (sync, revert, history, etc).
> Finally got around to writing this up:
> http://roscidus.com/blog/blog/2015/06/22/cuekeeper-internals-irmin/

Really nice!  I'm curious about whether this is a good time to pull out
the IndexedDB bindings into their own mini-library?  They would be useful
to provide a minimal Irmin backend without the rest of the CueKeeper code
to act as a guide.  Spiros (CCed) may be interested in this for a project
he's working on.

> I'd be particularly interested to hear about suggestions for avoiding
> the React GC issues.

These GC issues seem to be as old as FRP itself. A slightly higher-level
question: do you have any sense as to how well this model could be mapped
onto React.js and its virtual DOM model?

There seem to be a growing set of UI components that only use one-way data
flow and hence avoid the trap of leaking signals that seem to be quite
common when using <insert-flavor-of> FRP.

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.