koush

3 ms·

1. 1.▲
   by koush 15y ago

   This is certainly something that is doable and crossed my mind, but I did not want to have the await be restricted to functions that conform to the typical return arguments. For now at least.
2. 2.▲
   by koush 15y ago

   That's exactly how this was done. I'm going to implement "yield" as well when I have some time. They both just leverage coroutines.
3. 3.▲
   by koush 15y ago

   Not sure to be honest! I am still very new the to scene so I am unaware of this project. At first glance, we seem to have different approaches towards the same goal though.
4. 4.▲
   by koush 15y ago

   It exits the function, and resumes it when the callback completes. So other requests can be processed while the async function is (a)waiting.
5. 5.▲
   Fixing the callback spaghetti in node.js(github.com)

   222 points by koush 15y ago|101 comments
6. 6.▲
   by koush 16y ago

   This is the @koush referenced in the article. To repost what I said on reddit last week: "To clear up any confusion, I was not offered a job, just an interview, which I declined out of principle. For those saying "I'm going to regret being
7. 7.▲
   by koush 16y ago

   Oopsie, wrong link: http://www.koushikdutta.com/2009/01/microsoft-dlr-and-mono-b...
8. 8.▲
   by koush 16y ago

   Fairly old news. I ported Mono to Android a few years ago and got Python and Ruby running that way. http://www.koushikdutta.com/2009/02/monodalvik-interop.html