I don't need to "read" that's exactly what I meant: you can trust a
compiled package only if you have compiled it yourself, and have
previously checked the complete code or have it audited, which is
unlikely for both in most of cases, but happens systematically with js
for the compilation phase, while the check of the code, which does not
depend on tons of libraries, is trivial.
Le 21/07/2014 15:57, Maxim Kammerer a écrit :
On Mon, Jul 21, 2014 at 12:59 PM, Aymeric Vitte <vitteayme...@gmail.com> wrote:
Unlike obscure elefantesque open source code that you don't even know what
it becomes when it gets compiled, it's trivial to see what it is doing.
I suggest that you read about the process of just-in-time compilation,
which is Javascript engine browser- and version-specific.
--
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
--
Liberationtech is public & archives are searchable on Google. Violations of
list guidelines will get you moderated:
https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change
to digest, or change password by emailing moderator at compa...@stanford.edu.
