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
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. |
@metakeule I think asynchronicity is actually a feature of deno, given that @ry mentions support for top-level await. |
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. |
Is it like nodejs but for TypeScript and with blocking IO / without callback madness?
The text was updated successfully, but these errors were encountered: