diff options
Diffstat (limited to 'Docs.md')
| -rw-r--r-- | Docs.md | 90 |
1 files changed, 0 insertions, 90 deletions
@@ -400,93 +400,3 @@ gsutil acl ch -u AllUsers:R gs://denoland/608be47bf01004aa11d4ed06955414e9393451 See [CONTRIBUTING.md](https://github.com/denoland/deno/blob/master/.github/CONTRIBUTING.md). - -## Changelog - -### 2018.11.27 / v0.2.0 / Mildly usable - -[An intro talk was recorded.](https://www.youtube.com/watch?v=FlTG0UXRAkE) - -Stability and usability improvements. `fetch()` is 90% functional now. Basic -REPL support was added. Shebang support was added. Command-line argument parsing -was improved. A forwarding service `https://deno.land/x` was set up for Deno -code. Example code has been posted to -[deno.land/x/examples](https://github.com/denoland/deno_examples) and -[deno.land/x/net](https://github.com/denoland/net). - -The resources table was added to abstract various types of I/O streams and other -allocated state. A resource is an integer identifier which maps to some Rust -object. It can be used with various ops, particularly read and write. - -### 2018.10.18 / v0.1.8 / Connecting to Tokio / Fleshing out APIs - -Most file system ops were implemented. Basic TCP networking is implemented. -Basic stdio streams exposed. And many random OS facilities were exposed (e.g. -environmental variables) - -Tokio was chosen as the backing event loop library. A careful mapping of JS -Promises onto Rust Futures was made, preserving error handling and the ability -to execute synchronously in the main thread. - -Continuous benchmarks were added: https://denoland.github.io/deno/ Performance -issues are beginning to be addressed. - -"deno --types" was added to reference runtime APIs. - -Working towards https://github.com/denoland/deno/milestone/2 We expect v0.2 to -be released in last October or early November. - -### 2018.09.09 / v0.1.3 / Scale binding infrastructure - -ETA v.0.2 October 2018 https://github.com/denoland/deno/milestone/2 - -We decided to use Tokio https://tokio.rs/ to provide asynchronous I/O, thread -pool execution, and as a base for high level support for various internet -protocols like HTTP. Tokio is strongly designed around the idea of Futures - -which map quite well onto JavaScript promises. We want to make it as easy as -possible to start a Tokio future from JavaScript and get a Promise for handling -it. We expect this to result in preliminary file system operations, fetch() for -http. Additionally we are working on CI, release, and benchmarking -infrastructure to scale development. - -### 2018.08.23 / v0.1.0 / Rust rewrite / V8 snapshot - -https://github.com/denoland/deno/commit/68d388229ea6ada339d68eb3d67feaff7a31ca97 - -Complete! https://github.com/denoland/deno/milestone/1 - -Go is a garbage collected language and we are worried that combining it with -V8's GC will lead to difficult contention problems down the road. - -The V8Worker2 binding/concept is being ported to a new C++ library called -libdeno. libdeno will include the entire JS runtime as a V8 snapshot. It still -follows the message passing paradigm. Rust will be bound to this library to -implement the privileged part of deno. See deno2/README.md for more details. - -V8 Snapshots allow deno to avoid recompiling the TypeScript compiler at startup. -This is already working. - -When the rewrite is at feature parity with the Go prototype, we will release -binaries for people to try. - -### 2018.09.32 / v0.0.0 / Golang Prototype / JSConf talk - -https://github.com/denoland/deno/tree/golang - -https://www.youtube.com/watch?v=M3BM9TB-8yA - -https://tinyclouds.org/jsconf2018.pdf - -### 2007-2017 / Prehistory - -https://github.com/ry/v8worker - -https://libuv.org/ - -https://tinyclouds.org/iocp-links.html - -https://nodejs.org/ - -https://github.com/nodejs/http-parser - -https://tinyclouds.org/libebb/ |