Re:A web of trust for NPM
by stefan_ on Saturday October 03, 2020 @05:27PM
(#24674794)
Trying to solve the halting problem are we. Remember that one of the most dangerous JavaScript APIs turned out to be a sub-millisecond monotonically increasing time source.
[ Parent
| on HN ]
Solving the halting problem is quite tractable.
You can do it the right way, by using total functional programming. Or you can do it the wrong way, by providing a time budget or "gas", and yanking the process if and when it's exceeded.
No, this is more of a Rice's Theorem kind of situation...
Re:A web of trust for NPM
by 7373737373 on Sunday October 04, 2020 @04:20AM
(#24677279)
Why do you think using 'gas' is the wrong way? Not only does it solve this problem, it solves it in a deterministic way, which has many applications, for example deterministic debugging and replicable computation!
I don't, actually.
What I really meant was that total functional programming is the MIT way to do it, and gas caps or supervisors are the New Jersey way to do it.
Re:A web of trust for NPM
by matheusmoreira on Saturday October 03, 2020 @08:08PM
(#24675660)
> one of the most dangerous JavaScript APIs turned out to be a sub-millisecond monotonically increasing time source
Details?
Pretty sure that's a reference to the Spectre CPU timing attacks and JS's SharedArrayBuffer type being used to construct timers as an attack vector: