On top of which, not every "Event based" system isn't threaded.
They specifically provide fork/join as an example of Thread based. Scala 2.8 adds full support for using a fork/join model in Actors, which are... to the observer, event driven (message driven event responders backed by threads). Akka, a Scala framework which pulls in a more complete Actor model, Erlang style supervisors and a bunch of Clojure & STM data concepts (among other features) allows you to tune the underlying dispatch for their Actors. You can easily set it up to use thread pools.
Articles like this are going to cause, more than anything, your less-technical management type to suddenly decide event driven coding is bad for some reason. Without knowing that your code which APPEARS event driven on the outside may be thread driven on the inside...
They specifically provide fork/join as an example of Thread based. Scala 2.8 adds full support for using a fork/join model in Actors, which are... to the observer, event driven (message driven event responders backed by threads). Akka, a Scala framework which pulls in a more complete Actor model, Erlang style supervisors and a bunch of Clojure & STM data concepts (among other features) allows you to tune the underlying dispatch for their Actors. You can easily set it up to use thread pools.
Articles like this are going to cause, more than anything, your less-technical management type to suddenly decide event driven coding is bad for some reason. Without knowing that your code which APPEARS event driven on the outside may be thread driven on the inside...