Separating concerns

Last night, I realized that in my last post on messages, I skipped over one of the essential characters of message-passing APIs: that they separate the code that produces data from the code that acts on its availability with some level(s) of indirection. Consider the use of ‘Future<T>’ to produce values that are acted on…

1

F#

If you haven’t taken a serious look at F# yet, you should. This OCaml-inspired language is a great combination of OO and functional programming concepts and will challenge your thinking about how software could (and should) be built. Functional programming is very conducive to parallelization and this language is very much worth looking at. It’s now…

1

What About Today’s Gigacore Applications?

As should be clear from the previus post, I’m not a big fan of the threads + locks model. An alternative approach is the one offered by message-passing, which is used every day in distributed applications and with enormous success. The world-wide web is one giant concurrent application, if you will: millions of processors are…

2