Max Franz

Thanks for your consideration

Force directed layouts generally use a random seed for the simulation. It would be nice to have an option to set this value manually.

If building the worker from the blob fails, fallback on the simulated worker

The child-process impl works, but it's just a stopgap https://github.com/xk/node-threads-a-gogo/

`fabric.spread()` simply splits the array of data between the threads. Sometimes you have an array that contains items of varying processing expense. Using `fabric.pass( array.sort( byExpense ) ).spreadOneByOne( ... )`,...

`fn.name` becomes `fn.name || fn.toString().match(/^function\s*([^\s(]+)/)[1]`

This may make it unnecessary to use threads (e.g. threads-a-gogo) on Node.js: https://github.com/SyntheticSemantics/ems

https://hacks.mozilla.org/2016/05/a-taste-of-javascripts-new-parallel-primitives/