assembly graph

could be same, schemaless datastore?

Hello sql and cloure.set ns! ;P

very clojure-y mood, makes me think of clojure REBL (browser) which in turn is inspired by the smalltalk browser and was taken out of datomic (which is inspired by RDF, mentioned above!)

Yes, lisp!

This is my thinking as well i.e. if you could (a) keep parentheses but render them differently. But not going over board in basic view so it's still editable like text. AND also have a more graphical view.

Lisp! ;P

fahrvergnügen German for "driving-pleasure. Yes! ALSO This is kind of central, in two ways.

A. you need to have good story for mouse only and keyboard only B. you need to have multi-modal rendering

Now this is interesting. Instead of normal map here they've had to use this simple sketch/graph. Just arrows etc. BUT There maybe an actual value in that kind of simplicity!

Question worth asking here is why we have to see all the detail on the map always? Google may have different incentives than just showing you only essential data.

this is a benefit

I find it very interesting that the line for the gun control advocates and the gun rights advocates correlate so closely, it almost looks like a Rorschach test.

wow that is a scary statistic, out of 33,594 gun related deaths almost 23,000 of them were suicide.

that's insane to me that the US has more than double each of these other countries in gun related homicides.

most of the gun related crimes in the US are committed with hand guns not riffles, that totally goes against the stereotype.

Generation of diagrams and flowcharts from text in a similar manner as markdown. PlantUML equivalent in Javascript

Graph is extremely unclear. Bad usage of point shapes

Very nice review. Please note the reference [94] (Pantazatos et al.) is misplaced because they did not argue that spatial biases cannot entirely explain the putative links between CGE and functional segregation. Instead, they argued there was insufficient evidence in the original Richiardi et al. study linking elevated CGE with resting state functional networks, and that spatial biases may in fact entirely account for their findings. To describe the debate/exchange more accurately, I would suggest replacing the below sentence

“While spatial biases may contribute to these findings, as nodes belonging to the same module tend to be anatomically colocalized [7,8], they cannot explain these effects entirely [94,95].”

with the below paragraph:

“Spatial biases may contribute to these findings, as nodes belonging to the same module tend to be anatomically colocalized [7,8]. Pantazatos et al. argued that these findings are entirely explained by spatial biases [94]. They showed that elevated CGE, as defined in the original Richiardi et al. study, falls monotonically as longer distance edges are removed. Moreover, they showed that 1,000 sets of randomly spaced modules all have significantly high CGE when using the same null distribution defined in the original Richiardi et al. analyses. Therefore, elevated CGE is not specifically related to functional segregation as defined by resting state functional networks, which is in direct contradiction to the main conclusion of the original Richiardi et al. study. Since randomly placed modules do not align (spatially) with any distributed pattern of functional segregation, the finding of elevated CGE may instead be attributed entirely to anatomical colocalization of the nodes within each module. In their rebuttal to [94], Richiardi et al. argue spatial biases cannot explain their findings entirely [95]. However, the authors do not offer an explanation for significantly high CGE observed for randomly spaced sets of modules, other than to note that nodes tend to be closer on average compared to when modules are defined by resting state fMRI. Future work is required to dissociate the effects of spatially proximity on relationships between CGE and spatially distributed functional networks.”

this is the best named graph

Rohan indicated that procedures are also part of the graph. let us find out why.

what's the equation for that?

A forest is just a collection of trees. The main difference is that a forest does not necessarily need to be connected.

Sound like [Apache CouchDB]'s map/reduce output to anyone else?