fibers

One way to work around this is to use fibers and continuations which is what Quasar is doing.

> When newly built, the nest is a compact, deep cup constructed of plant down, spider silk and cocoon fibers.

Cardboard can be recycled, but each time it goes around, the fibers get shorter and it becomes more fragile.

This promotes crosslinking between collagen fibers making up the cornea, strengthening it and arresting the progression.

While Java 9 sadly won't include native JVM fibers or continuations, it will probably make the instrumentation process 100% transparent.

D has fibers which are used extensively and once again, it's a highly desired feature.

Or use fibers (lightweight threads) and enjoy the best of both worlds: simple, blocking code with the scalable performance of async.

Quasar doesn't impose any further restrictions (that's not its job -- simply to provide fibers), but a language like Clojure certainly does.

In particular, resistant starch and most forms of soluble fibers work fairly well.

If you schedule your coroutines based on the kernel scheduler, they're fibers.

Probably in brown rice (but then, they are packed in the fibers).

The fibers are longer and sharper and really sting and take a few freezing cold showers to really get it out of your skin.

I saw a presentation once arguing that fruits come with "the poison and the cure", in that the fibers counter the fructose.

Quasar lets you choose: fibers for transactions stuff, and plain threads for long-running computations, both are abstracted into what we call a "strand".

From the Quasar documentation: "Runaway Fibers A fiber that is stuck in a loop without blocking, or is blocking the thread its running on (by directly or indirectly performing a thread-blocking operation) is called a runaway fiber.

[1] "Quasar fibers are implemented by creating and scheduling continuation tasks and since the JVM doesn’t (yet) support native continuations, Quasar implements them through selective bytecode instrumentation: methods that can block a fiber currently need to be explicitly marked through annotations so that Quasar can insert the continuation suspension and resumption hooks."

Fibers and coroutines are different uses for the same thing.

Fibers which could do async IO coded in a blocking style (co-operatively tasked) would rock so hard that one day it has to work without sucking...

Performance has been a major focus of every release since 1.9.1; integrating Rubygems considerably helped with tooling and dependency issues; encoding-aware strings were a major feature of 1.9; coroutines and generators can be implemented more effectively with 1.9's Fibers.