This article is a little outdated. (2011; that should probably be in the title.) JS in the browser _does_ have a cryptographically secure random number generato

This article is a little outdated. (2011; that should probably be in the title.) JS in the browser _does_ have a cryptographically secure random number generator now, for example (Crypto.getRandomValues) and a secure way to generate and store keys (SubtleCrypto.generateKey). A lot of the article's other concerns are still valid, but there are a few new standards on the horizon which could eventually fix most of those and make cryptography in the browser viable, such as the Web Package standard. The Signed HTTP Exchanges standard's section on binary transparency is especially interesting for this use case: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#name-binary-transparency https://wicg.github.io/webpackage/draft-yasskin-http-origin-...