Prerender all the things

[main--]

so you don't need 1337GB of RAM to view some demos

[moritzuehling]

How will prerendering things will help? You need the raw data if you want individual selection to be possible. I think it'd be easier to just send the raw data, and let the client render it to save ram.

Disadvantage: Performance.

[main--]

Prerender literally everything, so all the client has to do is display a single image. Or maybe find the right balance between stored images on the server, on-the-fly server-rendered images and clientside rendering.

Because right now, client performance is abysmal, even user feedback says that.

[moritzuehling]

Maybe we should go away from JS and use sth. Ylike MonoGame...?

Am 2. November 2014 00:53:16 schrieb "main()" notifications@github.com:

Prerender literally everything, so all the client has to do is display a
single image. Or maybe find the right balance between stored images on the
server, on-the-fly server-rendered images and clientside rendering.

Because right now, client performance is abysmal, even user
feedback says
that.

---

Reply to this email directly or view it on GitHub:
#21 (comment)

[main--]

JS is definitely not the bottleneck, see Unreal Engine.

[main--]

To be honest, we shouldn't even have to prerender. Unreal Engine runs ezpz, our little heatmap magic is nothing compared to that.

[moritzuehling]

Fixed all slow stuff by simply just not using images.