Is it like nodejs but for TypeScript and with blocking IO / without callback madness?
metakeule
All 3 comments
I have a question as well. Is there a primary motivation behind the project? Of course, there needn't be one - the most common justification for coding (for me at least) is "just because".
I'm curious if there are specific aims. Could modification of the V8 engine to handle TS directly be on the roadmap? There would be obvious performance gains by executing TS directly.
kizerkizer
on 30 May 2018
@metakeule I think asynchronicity is actually a feature of deno, given that @ry mentions support for top-level await.
kizerkizer
on 30 May 2018
No. Async I/O is very necessary in javascript - there's only one thread.
The point of this project is to make a simpler (eg how modules are built) and more secure non-browser runtime. It's also built in 2018 instead of 2009, so it uses better 2018 tooling.
ry
on 30 May 2018
Related issues
motss
路
3Comments
davidbarratt
路
3Comments
ry
路
3Comments
amiteshore
路
3Comments
xueqingxiao
路
3Comments
Most helpful comment
No. Async I/O is very necessary in javascript - there's only one thread.
The point of this project is to make a simpler (eg how modules are built) and more secure non-browser runtime. It's also built in 2018 instead of 2009, so it uses better 2018 tooling.