Ian Mackenzie

Could probably just call the cache type `Scene3d`, with an API like ```elm -- Create an empty scene Scene3d.init : Scene3d -- Update a scene to include the given scene...

Never mentioned piping, I mentioned partial application 🙂 Piping is one use of partial application, but I think it can also be useful when doing things like mapping over `List`s...

A couple questions/thoughts (partially just thinking to myself here, but happy to take suggestions): - Would very short constructors like `Point2.xy` be changed to `Point2d.fromXY`? - Similarly, would `Point2d.meters` change...

Could also just rename `xy` to `fromCoordinates` - even longer (I think I remember you saying you were happy to move away from that name a while ago!) but pretty...

Perhaps use `lambertian / fwidth(lambertian)` for toon shading, as suggested by https://twitter.com/rickyreusser/status/1023852556060057600 (would require standard derivative support in the `webgl` package)

It would certainly be a useful addition, although I'd like to take some time to understand the implementation a bit (especially stuff like numerical stability). Can you share your current...

What are your thoughts on the various numerical issues described at https://en.wikipedia.org/wiki/Bentley%E2%80%93Ottmann_algorithm#Special_position_and_numerical_precision_issues? Polylines/polygons will certainly often have vertical segments and by definition will have segments with coincident endpoints. I think...

Specific improvements to make: - [ ] Replace `sceneProperties` in `constantPointFragment` with single `lowp` supersampling uniform - [ ] Replace `sceneProperties` in `emissiveFragment` and `emissiveTextureFragment` with separate `mediump` reference white...

Useful reference: https://github.com/xeokit/xeokit-sdk/wiki/High-Performance-Model-Representation (thanks @pixelpartner!)

Conversation with @danabrams on possible approaches: > ianmackenzie [10:51 AM] > Hey Dan - hope you had fun in Oslo! Looking forward to watching the various talks > How much...