sillysauce

I'm also a big fan of: http://slipsum.com/

Yes, files (or blocks) you request stick around on your computer. There is a garbage collection command that will remove unpinned files. There is also going to be (not sure if it's implemented yet) the bitswap. More information about the bitswap can be found in the paper.

This article kind of comes at a perfect time for me. I just recently started working on a project with a code editor and I've been battling for a while how to communicate changes through react.

I plan to use ace, and require the ability to get and apply patches as the user types into the ace editor, get code when they need to compile, as well as be able to modify other properties of the editor.

At the most complex level, I need to keep two ace editors in-sync, doing this with cure javascript and ace is simple, as you just need to apply a patch from one editor to the other.

Building large and complex applications has always been the big problem for me with React, and the author states it right up front

    we ran into issues finding examples of how React could
    apply to an application as complex as ours, given that
    most tutorials focus on the specifics of toy-sized demo
    apps as opposed to more general discussions of the
    problems specific to larger applications.

This is just something that is going to take time though.