3 ms·
Impressive work, but I really feel the kind of issues the author had to overcome are also the reasons for avoiding JavaScript in general programming (which woul
by romaniv 15y ago
Impressive work, but I really feel the kind of issues the author had to overcome are also the reasons for avoiding JavaScript in general programming (which would require quality RNGs).
- trebor 15y agoUnless I'm mistaken, he's laying the reason/groundwork for a replacement PRNG for Javascript/ECMAScript. If one of these algorithms were executed in the backend it would be quite fast and have none of "javascript slowdowns" for those calculations.
- acqq 15y agoNobody needs to do "the groundwork" of implementing the existing algorithms in JS if they would be "in the backend." The reason author did it was to have different algorithms, with their own good and bad sides, giving the same repeatable results on the existing platforms implemented in pure JS and with the common interface. Additionally he presented his own algorithm inspired by Marsaglia's MWC.