Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please explain... #17

Closed
metakeule opened this issue May 30, 2018 · 3 comments
Closed

Please explain... #17

metakeule opened this issue May 30, 2018 · 3 comments

Comments

@metakeule
Copy link

Is it like nodejs but for TypeScript and with blocking IO / without callback madness?

@kizerkizer
Copy link
Contributor

kizerkizer commented May 30, 2018

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
Copy link
Contributor

kizerkizer commented May 30, 2018

@metakeule I think asynchronicity is actually a feature of deno, given that @ry mentions support for top-level await.

@ry
Copy link
Member

ry commented May 30, 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 ry closed this as completed May 30, 2018
@kitsonk kitsonk mentioned this issue Jun 6, 2018
piscisaureus pushed a commit to piscisaureus/deno that referenced this issue Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants