kgryte
The Open-Source Ecosystem Canvas
AI and the invisible newcomer in open source
Re:Measuring the impact of AI on experienced open-source developer pro...
on Thursday July 17, 2025 @03:50PM (#44597425)
Here's a reflection from one of the study's participants, which covers some of the common criticisms and where he see opportunities for further study.
Lapack in the Web Browser
Re:Standard library for JavaScript and Node.js
on Sunday January 20, 2019 @02:55PM (#18955205)
For an example of using stdlib in Observable, see here: https://beta.observablehq.com/@kgryte/stdlib-real-time-k-mea.... Other notebooks can be found here: https://beta.observablehq.com/collection/@kgryte/stdlib.
Re:Standard library for JavaScript and Node.js
on Saturday January 19, 2019 @03:47PM (#18949071)
Re: native vs JS. I'd say it depends. For certain implementations, such as operations on large arrays, native implementations can provide performance benefits (see https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...). However, for other implementations, including common mathematical functions, implementing them in pure JavaScript can be more performant when running in Node.js, as you do not need to cross from JS to C/C++ (see https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...). Lastly, even if functionality is backed by native code, would still need JavaScript fallbacks in order to, e.g., allow for bundling and use in non-Node.js environments.
Re:Standard library for JavaScript and Node.js
on Saturday January 19, 2019 @01:14PM (#18948303)
Notable exceptions are R, Julia, MATLAB, Mathematica, etc. Namely, environments/languages which focus on numerical and scientific computing applications. One of the project's goals is to provide similar functionality on the web and in Node.js as those environments. Accordingly, in order to realize that goal, one needs to offer quality ("standard") implementations for doing mathematical operations (see https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...).
Aside: calling the library "essentially a statistics toolkit" is a mischaracterization given that the bulk of available functionality is not statistics. For example, lodash/async style utilities (https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...), iterator utilities (https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...), assertion utilities (https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...), benchmark framework (https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo...), etc. While certainly a WIP, might prove informative to peruse: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_mo....