I think these explorations are very worthwhile. People tend to underestimate how much work it takes to implement all the distribution functions.
Looking forward to seeing where this goes.
I'm hoping to see how the lib authors:
1.) deal with model workflow (for example, how do I go from model building to prediction?);
2.) explain what data structures they hope to introduce (if all the authors did was make a strong matrix library for server-side javascript, that would be enough to make everyone's day);
3.) outsource the computational grunt work to C (or Fortran, if they're really adventurous)
The core.js file will run server-side. It has no dependencies and has been included using "this", which attaches to Node.js' modules. So to use it in a script you would just have to add the following line of code at the top of your script:
var jstat = require('path/to/core.js').jstat;
As for outsourcing the grunt work to a C library... We're going to need some community involvement with that one. It would be nice to be able to compile that directly into the server, but it's not on our roadmap right now.
Looking forward to seeing where this goes.
I'm hoping to see how the lib authors:
1.) deal with model workflow (for example, how do I go from model building to prediction?); 2.) explain what data structures they hope to introduce (if all the authors did was make a strong matrix library for server-side javascript, that would be enough to make everyone's day); 3.) outsource the computational grunt work to C (or Fortran, if they're really adventurous)