Alex Kempton

Perhaps should consider having types as a sort of "plugin" style thing. They could live in folders and be a collection of functions/components that are called in various places throughout...

This new approach to value types is happening here: https://github.com/nudibranchrecords/hedron/pull/323 I think it's working quite well. Would be super easy to get strings in now. Vec3 and Vec2 not so...

Actually looks quite simple to implement... https://threejs.org/examples/webgl_worker_offscreencanvas.html

Definitely not simple. - All three.js related code (including sketches) will need to be run in a worker. - A params object will need to to be sent to the...

Workers as modules may be possible with a chrome flag switched on (this is possible with Electron)

- All params relying on inputs (e.g. a sin wave LFO) would still experience jank unless this was handled inside the worker. Any access to devices isn't possible though so...

MIDI in web workers being discussed here: https://github.com/WebAudio/web-midi-api/issues/99

MIDI could happen entirely in Electron main thread, _which is also a separate thread too!!_

Been solving some of this in `fix/component-performance` branch: - Updated styled components - Using memoized selector for params Could look for more cases where a memoized selector could come in...

Styled components still seem to be adding a lot to the time of each component mounting. Replacing option elements as simple divs rather than styled components massively reduces the mount...