> Python is not, as it can interact with native binaries
It sounds like what you actually mean here is that Python is equally as unsuitable and must instead use native binaries. Which one could just as easily do with JS...
A reasonable argument could be that such native binaries are available in the Python community and already in use as stable existing solutions, but that's more about ecosystem than language suitability.
Additionally, while I'm not too sure what convnet, node-mind, brain.js, etc. referenced in the article are using internally, there are gpu-oriented solutions being written in JS like https://www.npmjs.com/package/weblas
Python is dog slow. This is why it is used as a glue language for C modules. This is the canonical way to do things. Javascript OTOH is decently fast on its own, but you can't really interact with libraries written in C or FORTRAN, as far as I know.
Re:Neural Networks in JavaScript
by notduncansmith on Monday May 09, 2016 @10:50AM
(#11660237)
Node has been able to interoperate with C/C for some time, via node-gyp and node-ffi.
Cool, good to know.
Well, somebody could write a NodeJS library that talks to the GPU.
Atwood's Law makes it inevitable that someone will if no one has already.
Re:Neural Networks in JavaScript
by pjonesdotca on Monday May 09, 2016 @09:35AM
(#11659693)
Absolutely true.
https://github.com/kashif/node-cuda
Also of note: https://github.com/nikhilk/node-tensorflow
> Something that I do not agree with myself, as a Node.js and back-end JS developer
NodeJS mostly works when CPU time is not the limiting factor, that is, powering the Web. Neural network is the polar opposite.