I see your claims against all of that, some more obvious than others, some are a bit outdated. I&#x27;m not going to discuss the up and downsides. All I am saying is I don&#x27;t see any proof. No links, no references, no proof-of-concept JS manipulation. Nothing. Only accusations and assumptions.<p>When one makes quite huge accusations, as these are obviously, going strong against best practices laid out by researches, both from Google and Amazon (and probably a lot more), it would be better to not only hate-talk, but also - quite simply - proof. Show, for example, how you can intercept JS sent from the server via https. Or show how somebody did that. Or how you are going to XSS in any major JS Framework out there. Or at least link some examples when you make assumptions that all JS crypto won&#x27;t work because of things like<p>&gt; &quot;cross-site scripting&quot;. Virtually every popular web 
&gt; application ever deployed has fallen victim to this problem<p>XSS Sanitation was for long time a problem and, of course, it still is, when used the wrong way. There were plenty of hacks and attacks using cross site scripting, no doubt.<p>or<p>&gt; WHAT SYSTEMS PROGRAMMING FUNCTIONALITY DOES JAVASCRIPT LACK?
&gt; Here&#x27;s a starting point: a secure random number generator.<p><a href="https:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;WebCryptoAPI&#x2F;#dfnReturnLink-0" rel="nofollow">https:&#x2F;&#x2F;www.w3.org&#x2F;TR&#x2F;WebCryptoAPI&#x2F;#dfnReturnLink-0</a><p>... and so on ...