Tootfinder

»Math.random() is not so random — The Illusion of Randomness in JavaScript:
Don’t Trust Math.random() - Uncovering the Hidden Predictability of Random Numbers.«
In some applications random numbers are very useful but not unique and therefore you should consider where to use it. In this regard, there are for example, UUID v4 or Nano ID and the same.
🧑‍💻

Math.random() is not so random: The Illusion of Randomness in JavaScript
Don’t Trust Math.random(): Uncovering the Hidden Predictability of Random Numbers.

I am a bit surprised how high Javascript is in that list. Don't get me wrong, I am in the same camp, but I'd have thought people liked JS more.
(I just don't think the platform [as in runtime important tooling/libraries] is mature and it's too hype driven so I decided to check in in a few years when things might have settled more)

Cool things recently happened in #JavaScript land:
- https://www.infoq.com/news/2025/10/deno-2-5-released/ a new version of

Deno 2.5 Brings Support for Permission Sets and Test API Hooks
Deno 2.5 has arrived, enhancing the secure JavaScript/TypeScript runtime with new permission sets, refined testing hooks, and performance boosts. Upgrading to V8 14.0 and TypeScript 5.9.2, it unlocks

#JeffGarlin
Season 5 Episode 8 "K-GAS the Groove Yard of Solid Gold"
#RandomBaywatch #lvdlpx

I'm building webkit-gtk right now. It's one of these messy packages where a few source files need a lot of memory to compile, and ninja can randomly order jobs so that all of them suddenly start compiling simultaneously. So to keep things going smoothly without OOM-ing, I've been dynamically adjusting the available job count via steve the #jobserver.
While doing that, I've noticed that ninja isn't taking new jobs immediately after I increased the job count. So I've started debugging steve, and couldn't find out anything wrong with it. Finally, I've looked into ninja and realized how lazy their code is.
So, there are two main approaches to acquiring job tokens. Either you do blocking reads, and therefore wait for a token to become available, or you use polling to get noticed when it becomes available. Ninja instead does non-blocking reads, and if there are no more tokens available… it waits till one of its own jobs finish.
This roughly means that as other processes release tokens, ninja won't take them until one of its own jobs finish. And if ninja didn't manage to acquire any job tokens to begin with, it is just running a single process via implicit slot, and that process finishing provides it with the only chance to acquire additional tokens. So realistically speaking, as long as there are other build jobs running in parallel, ninja is going to need to be incredibly lucky to ever get a job token, since all other processes will grab the available tokens immediately.
This isn't something that steve can fix.
#Gentoo #NinjaBuild

Clutch Control: An Attention-based Combinatorial Bandit for Efficient Mutation in JavaScript Engine Fuzzing
Myles Foley, Sergio Maffeis, Muhammad Fakhrur Rozi, Takeshi Takahashi
https://arxiv.org/abs/2510.12732

Clutch Control: An Attention-based Combinatorial Bandit for Efficient Mutation in JavaScript Engine Fuzzing
JavaScript engines are widely used in web browsers, PDF readers, and server-side applications. The rise in concern over their security has led to the development of several targeted fuzzing techniques. However, existing approaches use random selection to determine where to perform mutations in JavaScript code. We postulate that the problem of selecting better mutation targets is suitable for combinatorial bandits with a volatile number of arms. Thus, we propose CLUTCH, a novel deep combinatoria…

Just finished up final polish on first release of my anarchy RNG library in Lua! Have you ever wanted an incremental or reversible shuffle? I've got one for you :)
Lua REAME page w/ links: #coding #rng #random