mirror of
https://github.com/denoland/deno.git
synced 2024-12-23 07:44:48 -05:00
Add milestone 2 to roadmap
This commit is contained in:
parent
8020f5fc0b
commit
ac0910e03c
1 changed files with 17 additions and 1 deletions
18
Roadmap.md
18
Roadmap.md
|
@ -76,7 +76,7 @@ Program requests to spawn `rm -rf /`. Grant? [yNs]
|
||||||
|
|
||||||
## Milestone 1: Rust rewrite / V8 snapshot
|
## Milestone 1: Rust rewrite / V8 snapshot
|
||||||
|
|
||||||
ETA: July 2018.
|
Complete! https://github.com/denoland/deno/milestone/1
|
||||||
|
|
||||||
Go is a garbage collected language and we are worried that combining it with
|
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.
|
V8's GC will lead to difficult contention problems down the road.
|
||||||
|
@ -92,6 +92,22 @@ startup. This is already working.
|
||||||
When the rewrite is at feature parity with the Go prototype, we will release
|
When the rewrite is at feature parity with the Go prototype, we will release
|
||||||
binaries for people to try.
|
binaries for people to try.
|
||||||
|
|
||||||
|
|
||||||
|
## Milestone 2: Scale binding infrastructure
|
||||||
|
|
||||||
|
ETA: 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.
|
||||||
|
|
||||||
|
|
||||||
## libdeno C API.
|
## libdeno C API.
|
||||||
|
|
||||||
Deno's privileged side will primarily be programmed in Rust. However there
|
Deno's privileged side will primarily be programmed in Rust. However there
|
||||||
|
|
Loading…
Reference in a new issue