Hacker News new | past | comments | ask | show | jobs | submit | more jonenst's comments login

Couldn't you use plot "./out.csv" using 1:2 with lines to have the same line graph with gnuplot ?


For sure! I actually think I prefer the points over the lines, since the lines make you think that there is data where there isn't.


It's a nice visualization, but cpu usage shoots through the roof ! Deleting the animated arrows between the countries helps a bit, but then it still uses around 50% cpu (and that's on a fast desktop computer. Can't imagine my laptop trying to display this page). Using Ubuntu + firefox (it's a little better with chromium).

Is it a problem with this page ? With my setup ? Or is it just impossible to do something of this quality on the web without monster cpus ?


Hi there,

I'm the author of the map. For sure it can be optimised. If you can help, feel free to do so on github - or reach out so we can chat. Thanks :)


Same here. It was already sluggish and using a lot of CPU power but as soon as I clicked on the check-boxes the whole thing ground to a halt... took 30 seconds to close the tab.

I really like the idea though.


It runs fine for me on a Celeron-based Chromebook, albeit with 100% usage of one core.


The fan is going crazy on my laptop with an older i5, but it works.


Wow, this article is bad. And the comments are so positive, one has to wonder how many come from the writer's friends...


This has to be a troll. Both snippets of code given in page 2 are pretty readable and self-documented. The author didn't provide an implementation of the same algorithm in an imperative language. I'd be ready to bet that the comparision wouldn't be to the advantage of the imperative language.


I feel that this is a good example of Rich Hickey's simple-vs-easy disjunction. If you are an experienced java programmer, then it is easy to understand code with a similar syntax to java. Code with a foreign syntax will be initially very difficult to understand, even if it has simpler semantics.


I agree that the basic problem is familiarity. Even beyond syntax, OO code carries with it a certain set of idioms that are obvious to anyone versed in an OO language (e.g. instantiation). Likewise, functional programming has its own idioms that are not obvious to someone not versed in any functional language.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: