I had this idea 8 years ago during a busy winter in Vienna, Austria where I couldn’t see the Sun for two consecutive weeks (buildings are rather high and streets narrow). I just wanted to know where I could spend lunch break in the Sun. Eventually started programming it around 2 years ago.
It’s a web-app based on three.js. Think of Google Earth enhanced by time based solar shadows. While there is global terrain coverage, buildings are currently limited to Vienna but we’re working on global coverage as well.
This argument is wrong on so many levels. Why deal with massive shit just because there is even more massive shit in place at the moment. Fix the root cause.
This 16y old boy builds a sweet website – good enough to reach #1 on this page – just to push his goal of a year in CA and you offer an introductory "… causes Chrome to lag". Come on, that's better stuff than I see from some 'professionals'.
"With high-DPI displays, the aliasing problem caused by insufficient pixels has been extinguished." that's not true. Aliasing is an omnipresent problem in discretized data every rasterized display is based on. Even though a retina display samples at a much higher rate, it needs anti aliasing for optimal results.
I'd like 64bit displays too. The problem is that there's quasi no content and also no content pipeline. Someone has to take the first step here.
