Julian Mazzitelli

@hirako2000 for cpu generative textures like this https://jmazz.me/codevember/2016/19/ source: https://github.com/thejmazz/threejs-starter-pack/blob/e60ad6f66a11f60c928b20ee70bd9ce869d5d502/src/index.js#L142 Useful to use CPU based random functions since there are some quirks with GPU implementations of PRNG. But for simplex/perlin...

https://medium.com/dailyjs/the-mandelwat-set-c3037204bf83

so can use jest style? with `__spec__` (or similar) folder alongside code

This looks cool - was not aware there was a flow -> asm tool. However may not provide much performance boost if underlying Three itself is not also written as...

rStats captures webgl details, not just fps

Probably good to also add some examples using webgl 2 features, like - [ ] transform feedback http://www.realtimerendering.com/blog/webgl-2-new-features/

Instead, maybe abstract it so PP passes can take in fragment shader code As opposed to defining a key in some module for all these passes

However, looking at wagner API, maybe I spoke too soon

the source of our current `PostProcessorModule` is very similar to that of Wagner. I suspect ours came from `THREE.EffectComposer`, which Wagner is built on. Might be worthwhile to deprecate `PostProcessorModule`...

Not just for Node, but just b/c it allows toggling debug logs with environment variables. could have different logs turned off for different test cases for example, or if you...