Michiel Helvensteijn

> Unfortunately, passing a JSON object from thread to thread natively is as simple as the browser stringifying the object and passing the string between threads, then parsing it on...

Even if you do not want to give up your own parser/renderer, and compatibility with other Markdown flavors, a 'GitHub option' would be quite useful. This option would simply override...

FYI: Here you can find an up-to-date css file you can use: https://github.com/sindresorhus/github-markdown-css Pretty nifty. It is [automatically generated](https://github.com/sindresorhus/generate-github-markdown-css) from GitHub itself.

I'm also experiencing this problem. At the very least, an `"update"` method seems sensible.

Seems like you should be able to _explicitly name_ the iterator. That way you could do multiple levels of nesting. Here's the operation for "non-empty intersection": ``` { some: ['i',...

@BenjaminHCCarr: Unix standard? I don't think that's true. I don't know about FreeBSD, but both on my Linux box and my Macbook, deleting one of the references of a hard...

This seems to be the case for any change: http://jsfiddle.net/mhelvens/7q9rrLya/1/ That's pretty important.

Hi, This makes sense to me. In fact, some plans exist for a version 2.0, and if I ever get to that, I will probably write it in TypeScript, and...

Sorry for the delay in responding. First thought: Moving the source-code away from ES6 modules is like taking a step backward. Your motivation is to be able to load the...

The `[from, to]` representation also goes for methods that need to pass it to callbacks: - `equals` - `mergeIn` - `clone` - `transitiveReduction`