Cool visuals, as with everything like this where the creator probably just churned open datasets through LLMs there are many inaccuracies particularly around borders.
An interesting effort though, and at least this one has a decent page about sourcing.
Grumble about the graphics choices: dark-grey-on-black-with-other-dark-colors is a terrible color scheme, that renders the borders nearly invisible.
There's a reason print maps have a standard set of colors, with very light blue for oceans, white for land backgrounds, and a variety of dark colors for features. The "modern white-on-black web aesthetic" only really works for text- and figure-heavy pages, where you must then use very light colors (white, yellow, light orange, light green) for features/lines.
> Also, the 19th century was far more conflict-prone than I thought.
Let me guess, you're American? For the US, once Northern America was settled, the US established and the conflicts with Natives and the Brits resolved, all you had was the Civil War...
But here in Europe, up until 1945, it was constant warfare. And that not just the large wars between entire countries that some czars or emperors drew up, there were also countless unnamed skirmishes and dealings between all the countless fiefdoms.
Interestingly, this website reliably crashes my firefox on linux while consuming 55GB of memory.
Claude's TLDR of what's causing the problem (may or may not be accurate): "That animation loop is almost certainly leaking memory: each time-step it draws new border geometry (GeoJSON/vector shapes) but doesn't free the old frames, so RAM climbs without bound. When you interact — especially auto-playing the timeline — the tab grows until it swallows all 62 GB of RAM + swap and the kernel kills it."
Cool visuals, as with everything like this where the creator probably just churned open datasets through LLMs there are many inaccuracies particularly around borders.
An interesting effort though, and at least this one has a decent page about sourcing.
Grumble about the graphics choices: dark-grey-on-black-with-other-dark-colors is a terrible color scheme, that renders the borders nearly invisible.
There's a reason print maps have a standard set of colors, with very light blue for oceans, white for land backgrounds, and a variety of dark colors for features. The "modern white-on-black web aesthetic" only really works for text- and figure-heavy pages, where you must then use very light colors (white, yellow, light orange, light green) for features/lines.
Mercator police: please do not use projection that makes Greenland 14x bigger than reality and e.g. Russia 2x. See here https://www.visualcapitalist.com/mercator-map-true-size-of-c...
Robinson Projection would be much more accurate.
This is really neat. Also, the 19th century was far more conflict-prone than I thought.
> Also, the 19th century was far more conflict-prone than I thought.
Let me guess, you're American? For the US, once Northern America was settled, the US established and the conflicts with Natives and the Brits resolved, all you had was the Civil War...
But here in Europe, up until 1945, it was constant warfare. And that not just the large wars between entire countries that some czars or emperors drew up, there were also countless unnamed skirmishes and dealings between all the countless fiefdoms.
Interestingly, this website reliably crashes my firefox on linux while consuming 55GB of memory.
Claude's TLDR of what's causing the problem (may or may not be accurate): "That animation loop is almost certainly leaking memory: each time-step it draws new border geometry (GeoJSON/vector shapes) but doesn't free the old frames, so RAM climbs without bound. When you interact — especially auto-playing the timeline — the tab grows until it swallows all 62 GB of RAM + swap and the kernel kills it."
I love this. Did you make it? Why?
War is a racket.
This is cool.