That's a nice explanation Somi. You've made the main idea clear without delving into the specifics of the event loop or the complexities of the tread pool itself.
One thing I would like to mention here though, tokio for Deno is what libuv was for Node and as far as my understanding goes, each and every async operation is not run in the tread pool.
Things like networking calls are usually handled directly by the operating system and things like file system calls are handled by the thread pool.
This is something important to know because depending on where the operation is being run, it'll have certain limitations. Also the type of operating system makes a difference. OS calls on *nix system handle different operations than windows system.
And there's a vital typo in the article. Please do look out for that.
Again, nice article. Well done.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's a nice explanation Somi. You've made the main idea clear without delving into the specifics of the event loop or the complexities of the tread pool itself.
One thing I would like to mention here though, tokio for Deno is what libuv was for Node and as far as my understanding goes, each and every async operation is not run in the tread pool.
Things like networking calls are usually handled directly by the operating system and things like file system calls are handled by the thread pool.
This is something important to know because depending on where the operation is being run, it'll have certain limitations. Also the type of operating system makes a difference. OS calls on *nix system handle different operations than windows system.
And there's a vital typo in the article. Please do look out for that.
Again, nice article. Well done.