nni

good point - but if you actually search for "rabbit chasing dog", you do get a rabbit chasing a dog video - https://www.youtube.com/watch?v=GBYdaPacHJg, as well as some for the other way around

In this case, could you even know which one was actually meant?

Technically, I'd think that the ambiguity is removed when you use "rabbit-chasing dog", but that is assuming the text available is sufficiently precise.

here's a short video on "DisCoCat" - https://www.youtube.com/watch?v=99keybEZN4g

yep - the post-mortems on these things are always interesting

I've only very rarely seen performance issues with VSCode...

As far as using other abstractions, you're at the mercy of the developer(s) who made the abstraction, and I've found having to do lots of extra work to figure out how to inject desired customization that makes it generally worth it to just use d3 in the first place

very cool - trying it out, listening to the first session - hoping I'm not in a Black Mirror episode...

I've been seeing folks get excited about this, and haven't yet been able to see why it is so interesting. However, the people behind it (Bret Victor et al) and who I've seen playing with it are too interesting for me to ignore this...

sorry -here's one I listened to yesterday

- https://www.youtube.com/watch?v=oh-dcCeR-r4&t=6856s

basically, I search for "cognitive enhancement music"- sometimes the "meditation" ones seem nice, too. I have an immediate relaxation response to this stuff, and it's pleasant.

What about that ambient/"cognitive/aural beats" stuff on youtube? I've been trying that lately and it seems nice. No data to see if better or not, but definitely more relaxing.

I've also started just using earplugs which can also seem to be (subjectively) effective.

Note: This has not been tweaked for mobile devices, but seems to work (slowly) on an iPad. Built with d3, Mathjax, jstat.js

that is also an interesting idea I may do

You might find this interesting - it adds a bit of dynamicness to it

http://learnforeverlearn.com/candle/

Background:

I have begun a small project whereby I am looking to (subjectively) quantify on a scale of 0 to 10 different properties of images/situations that may be considered "ironic" by some. The current properties include things like "twinge of irony", incongruity, unexpectedness, etc. My longer-term goal is to play with some data visualizations based on the data.

Some rough notes on the origin of this project are at http://thoughtsonirony.blogspot.com/2016/02/towards-subjecti...

You can submit your own example(s) with your own values for the different properties (you don't have to give values for all of them). The example can be an image or the description of a situation. If you want, you can submit your contact info with your example, or just do it anonymously (for now, these values are being posted into a google docs spreadsheet that will be imported later to the list for the site and used as a basis for future data visualizations).

Also - if there are other properties that you think should be included, please let me know.

This is a viz put together based on the streaming data available via Matthew Roth's emojitracker streaming api.

He also has a nice writeup on how he put emojitracker together at https://medium.com/@mroth/how-i-kept-building-emojitracker-c...

emojitracker itself is at http://emojitracker.com/

thanks as well. These are nicely approachable writeups, starting from a basic level.

yes I was having to read the real HN much more carefully right after I played with the simulator

that's a good link - thanks

A sample three.js viz is at https://learnforeverlearn.com/splitdepth/

I looked again at this and it seems to be correct, based on Wikipedia etc. It's a weird tree that had some serious genetic consequences for Charles II - here's one note on that: http://blogs.discovermagazine.com/gnxp/2009/04/inbreeding-th...

btw, if you "pin" a person so that the popup remains showing, you can click on the name to do a google search of that person.

Hi 314

Even for this early version I had debated whether it was worth it to do it for descendant tree due to clutter issues (it can still happen for ancestor trees, but the heuristic limits used make this a little rarer). I'm not quite sure I understand what you're suggesting though - the curves coming into the top do terminate at the birth year, but the node itself kind of covers this up - is that what you're referring to?

A little background info about this is at http://www.nowherenearithaca.com/2015/07/displaying-lifespan...