Reword.
This commit is contained in:
parent
d898c14694
commit
52641fcece
1 changed files with 3 additions and 11 deletions
14
Technology
14
Technology
|
@ -122,20 +122,12 @@ infrastructure](https://www.freebsd.org/news/2012-compromise.html),
|
||||||
|
|
||||||
### Performance
|
### Performance
|
||||||
|
|
||||||
OCaml code is compiled to native code running in the OCaml runtime, which is
|
OCaml code compiles to native code running in the OCaml runtime, which is
|
||||||
very performant, on par with C++ code. The OCaml runtime is just used for
|
as performant as compiled C++ code. The OCaml runtime is just used for
|
||||||
memory management, and very small compared to a JVM or Python runtime. As
|
memory management, and very small compared to a JVM or Python runtime. As
|
||||||
example, our TLS library has up to 85% of the bulk throughput of OpenSSL (using
|
an example, our TLS library has up to 85% of the bulk throughput of OpenSSL (using
|
||||||
AES128-CBC). The TLS handshake performance is equal with OpenSSL.
|
AES128-CBC). The TLS handshake performance is equal with OpenSSL.
|
||||||
|
|
||||||
OCaml code can be very fast (our TLS implementation reaches up to
|
|
||||||
85% of the throughput of OpenSSL), and compiles either to native code on various
|
|
||||||
architectures or to bytecode. It can even compile to JavaScript. OCaml is
|
|
||||||
memory managed, individual developers don't have to manually allocate and
|
|
||||||
release memory (which is a common source of security issues in other operating
|
|
||||||
systems).
|
|
||||||
|
|
||||||
|
|
||||||
### Dependency management
|
### Dependency management
|
||||||
|
|
||||||
OCaml has a unique module system. A module specifies abstract datatypes
|
OCaml has a unique module system. A module specifies abstract datatypes
|
||||||
|
|
Loading…
Reference in a new issue