koush

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.

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.

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.

It exits the function, and resumes it when the callback completes. So other requests can be processed while the async function is (a)waiting.

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 principled", etc. Probably not. Android App sales have been more than good to me. Good, enterprising, devs should never find themselves short of opportunities."

I wasn't trying to "ride on the geohot wave to get 15 mins of fame". Without beating my drum too much, I've already achieved a moderate degree of it within the Android community. http://twitter.com/#!/koush

I had been tweeting about geohot's happenings for the past few months, and then I got that recruiter email. So I responded, and took a screenshot because the whole thing was a pretty ironic, and tweeted it. Then ~16000 followers made it go viral: http://twitter.com/#!/koush/status/46345951819993088

Oopsie, wrong link: http://www.koushikdutta.com/2009/01/microsoft-dlr-and-mono-b...

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