<story><title>GPU.js</title><url>https://gpu.rocks/#/</url></story><parent_chain></parent_chain><comment><author>Lerc</author><text>I have been using GPU.js in the last few weeks and I feel like there are two parts to the magic that makes it work.&lt;p&gt;The headline feature is the translation of JavaScript into Shader code, but the underlying architecture that interfaces between arrays and textures is I think where the utility really comes in for me.&lt;p&gt;I think I&amp;#x27;d actually be better off working with just that second part.  Writing the kernels in a more native shader language but being able to pass in arrays and get arrays out the other end.&lt;p&gt;While the aspect of writing the shader itself in JavaScript is cool when you consider what it has to do to make it work,  when it doesn&amp;#x27;t work it can be a real struggle to find out why.&lt;p&gt;Also there seems to be a bit of bit-rot in the documentation the link for the API reference is &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;doxdox.org&amp;#x2F;gpujs&amp;#x2F;gpu.js&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;doxdox.org&amp;#x2F;gpujs&amp;#x2F;gpu.js&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>GPU.js</title><url>https://gpu.rocks/#/</url></story><parent_chain></parent_chain><comment><author>SavantIdiot</author><text>This was posted multiple times on HN over the past 5 years.&lt;p&gt;And every time I see it, I cry that JavaScript doesn&amp;#x27;t have something like numpy.&lt;p&gt;numpy is just so damn logical and fast (and comprehensive!) that i don&amp;#x27;t consider myself a python programmer, i&amp;#x27;m a numpy user.&lt;p&gt;EDIT: (removed complaint). That said: this looks like a good foundation for someone to use for implementing a fully featured numpy in JS.</text></comment>