There were some nice videos in the recent years. It's an exciting thing to receive "for free".

So just write first semester CS synchronous code and and execute it on a dedicated fiber.

I wonder how Clojure will work with Loom when it comes in

@dharrigan Via Java interop and then probably a wrapper library. Clojure has to continue running on older JDKs for a long time so nothing in Clojure can change to leverage Loom directly until sufficient users are on that newer JVM.

I see

so the ability to use a library would make sense

pick and choose 🙂

Someone (maybe @ghadi?) posted a Gist of some code that would wrap/leverage fibers and it was pretty simple.

should be something like: Socket.accept(Fiber.spawn(() -> doStuff(s)))

Will it even be that? My cursory understanding was the majority of the changes are under the hood so to speak, so you would use the socket API as normal, and if you call accept from within a fiber it does all the callback stuff internally in the jvm

that's right @hiredman -- most Socket.read() and j.u.c.ReentrantLock.lock() usages would be seamless

The http request handler tying up a Thread would instead launch a fiber, no problem