4 ms·
"The missing JS randomness library" is a provocative subtitle. :) Have you compared your project to Random.js? https://www.npmjs.com/package/random-js https://w
by re 3y ago
"The missing JS randomness library" is a provocative subtitle. :) Have you compared your project to Random.js? https://www.npmjs.com/package/random-js https://www.npmjs.com/package/random-js There's also Rando.js but that project also appears to use a biased algorithm.
- EarthLaunch 3y agoThanks for mentioning others. The main thing I love about OP's library is the simple, clear naming. A lot of complexity has been solved for me. Looking at random-js, the barrier to entry is higher. I've looked at randomness libraries and that's the feeling they gave me: That I would need to learn how randomness works, rather than just calling a function for what I want; a random int, a weighted random. Cmd+F "weighted" doesn't find anything on both of those projects' readmes. There's a tradeoff for simplicity, but in many cases I'll take it. This is the iPhone of randomness and that's what I needed to feel comfortable using it rather than rolling my own.
- quickthrower2 3y agoI was thinking "if there is one feature JS doesn't have, it is a missing library"
- chriscavs 3y agoThanks for the comment! Yes it is a bit of a provocative title hahaha. i don't believe my library can be compared to random-js, since the goals of each are very different. random-js wants to provide the "engine" that replaces Math.random. I want to provide a library of utilities that are engine-agnostic. you can pull in random-js and use their engines to power aimless.js, as an example.