Browse Source
Merge pull request #1945 from svaarala/bytecode-doc-wording
Clarify bytecode use motivations
pull/1949/head
Sami Vaarala
6 years ago
committed by
GitHub
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with
5 additions and
1 deletions
-
doc/bytecode.rst
|
|
|
@ -81,12 +81,16 @@ executed:: |
|
|
|
When to use bytecode dump/load |
|
|
|
============================== |
|
|
|
|
|
|
|
There are two main motivations for using bytecode dump/load: |
|
|
|
Generally speaking, there are two main motivations for using a bytecode |
|
|
|
dump/load mechanism: |
|
|
|
|
|
|
|
* Performance |
|
|
|
|
|
|
|
* Obfuscation |
|
|
|
|
|
|
|
Duktape's bytecode format improves performance compared to compilation, but |
|
|
|
is not ideal for obfuscation as discussed in more detail below. |
|
|
|
|
|
|
|
Performance |
|
|
|
----------- |
|
|
|
|
|
|
|
|
