For those who may be baffled at the result, it comes from parseInt accepting two arguments (string & radix), and map providing three per iteration (the value, index and whole array).
The whole array is omitted, but the radix passed to parseInt is respectively 0, 1 and 2.
Valid radix values are 2 to 36, but somehow 0 is also accepted due to its falsiness, and defaults to base 10. Base 1 is definitely not valid so NaNs out, and 10 in base 2 (binary) is 2.
For more of those WTF moments, in JavaScript and other languages, check out "Wat" [1], another hilarious lightning talk by Gary Bernhardt.
This is incredible. Is there any way to use this directly from an encrypted img file on some remote computer (e.g. dropbox url)? It seems that 'network block devices' might help in that area, but it's unclear. Would be neat for industry to have a e2ee repo of many computers that can be streamed encrypted to a browser for working in.
> This rewrite is still even more work-in-progress than the original one and still does not support block devices.
Unfortunate (if understandable; none of this is criticism!). What does it do for disk, then? Or is it early enough to just not solve that and only use a bare kernel+initrd?
For those who are new to this, the classic article on this kind of phishing is The Line of Death [0]. Basically, the phishing site can create false title and URL bars.
[1] https://www.destroyallsoftware.com/talks/the-birth-and-death...