There have however been quite a few high profile cases of whether you are considered a resident of Denmark or not, after leaving Denmark -- something that has hit a golf player, a model and apparently 100 others whose cases were handled internally by the tax authorities.
In a blink of an eye, you can become a tax evader and essentially lose everything you've earned plus be sentenced to years in prison... unless you're the husband of the prime minister (who worked in Switzerland, paid no tax in Denmark yet essentially lived here).
So if you're leaving Denmark for Silicon Valley to run your startup, get legal help to ensure you won't suddenly get taxed for all your US-earned income because your left your wife/girlfriend in Denmark, visited her and say, answered a few emails or spent some money.
5 out of 31? And I'd say only 3 are noticeably slower, and only 1 seems to be "much" slower (at 0.38ms). But given that just about everything benchmarked seems to be sub-0.05ms, I'm left thinking that gaining noticeable and much-increased performance is highly dependent on operations, and a high-precision timer. Humans aren't going to notice a difference between an operation lasting 0.04ms vs 0.02ms. Unless a ton of operations add up to something noticeable, of course.
After looking into it further, morphdom appears to be a solid alternative to virtual DOMs. Seems worth having around for that reason alone, especially if it were to improve with time, or become used by other tools.
If possible, send it off to a web worker? That free's up the UI thread
Edit: So it's the rendering that's hard on the CPU. Canvas would probably improve performance. Also, the graphic is so simple and there doesn't seem to be any event listeners on the edges themselves, that converting should be trivial :)
For the most part you're not doing live animations, statically drawing on a 3 canvases would give you what you want (without huge overhead of DOM nodes and simplicity of 2D canvas painting). Web workers aren't going to do much since most of your lag is coming from way too much DOM (causing layout, repaints to take forever).
Now, I know that DNS can be a little bit scary when you dig into the details, and sure, it can be a little verbose, but it's not so bad that it's immoral!
Seems like another kitchen sink library to me... Demos are impressive, but when is someone going to write a JS viz library in a more declarative fashion like outlined in Grammar of Graphics? They all seem overly imperative (draw this pixel, then that pixel) or rigid, non-composable functions taking huge configuration JSON blobs.
I agree it's a barrier to have such crazy prices, but there are free resources available, especially on a topic as popular as Grammar of Graphics. Hadley Wickham (in my mind, synonymous with the concept, since he implemented Wilkinson's ideas in R's ggplot package), for instance, has numerous materials on it, including a short primer (http://vita.had.co.nz/papers/layered-grammar.pdf). It might not be as exhaustive as the Wilkinson text, but surely there's enough material out there to implement GG in JS, especially considering there's successful implementations in other languages?
