It already exists -> The stock market.

Key word in OP: PREDICTION.

It was my conclusion as well. I only found async useful in situations when a service has to deal with a large number of incoming requests, e.g. web server

I say you dodged a bullet. Imagine working under this person.

> Anyway, this is much longer than I meant, but my conclusion is that I'll continue to use async/await for web apps and REST APIs (because, why not), but for services, I'm going back to the threadpool, green threads and synchronization primitives, and only using async/await in a limited way where it provides clear value - not async all the way down from the entrypoint.

AFAIK, .Net doesn't support "green threads" and they repeatedly confirmed that there are no future plans to do so. Additionally, M:N threading model has serious interop issues as evident in Go, which is a no-go for system languages. Personally, I don't see a need for green threads since kernel threads are fast enough and don't use that much RAM as people tend to believe. And when they are not, sure, go async/await.

TIL: I've been using the term "green threads" incorrectly for years! [0]

I had actually meant "normal", OS-level threads.

[0] https://stackoverflow.com/a/42454139/25758

I used to use Ruby for small (100-500 loc) scripts to parse various CSV/JSON documents. You craft a couple perfect stanzas of immaculate code to do what you need and you feel great. Then you run it and turns out you forgot an `end` somewhere. Fuck. You run it again, and the name of the hash map variable is unknown, because you changed it at the last moment to make it more descriptive. Fuck. There, fixed everything. Run it again. Running for a couple seconds now with no errors -- pop the champagne! Wait, what's that? Row #998 of 1000 had an unexpected type of value? Fuck. Fix it, ship it. Wheel, snipe, and celly.

At some point I just started writing these things in Rust instead. Describe what I want deserialized as a struct. List the fields I want as enum variants. What's that, rustc, the "name" field is optional? Ok, that makes sense, I'll handle this right away. Done. Hey, rustc, how come people talk about fighting you all the time when you're actually the world's greatest pair programmer?

Borland C++ and Turbo Vision were a killer combo back in the DOS times. Borland's decline over the years was painful to watch. I guess that what happens to the engineering driven companies that get overtaken by the MBA types.

You purposely set them very low, then "beat" them and watch stock price go to the moon.

> Because Amazon is comparatively low-margin vs. other tech companies, improved revenue has a much greater effect on earnings.

Are you saying that 10% revenue increase has led to 10x earnings beat? That doesn't make any sense.

How does basic arithmetic not make sense?

If you were expected to make $1.01 and spend $1, and instead you made $1.10 and spent $1, your revenue only beat by 9% but your income beat by 900%.

If a lot of their costs are fixed it makes sense.

Or, they are simply gaming H1B and/or employer-sponsored Green Card application process that requires submitting a proof that they couldn't find a US citizen.

C# with .Net Core seems to fit the bill.