PUBLIC MARKS with tags blog & concurrent

# Why is the standard Scala actor implementation so complex when others have done it in a such simpler fashion? # Is it better to have one, big actor library that supports a wide variety of use cases, or a bunch of smaller ones targeted at specific niches and programming styles? # If there are to be a bunch, should they just be conceptually similar (e.g. all based on the actor model), or should there be interoperability among them?

Map/Reduce

A Rubyist dabbles in today's most exciting programming language