As processors become faster and multiprocessor systems become cheaper, the need to take advantage of multithreading in order to achieve full hardware resource utilization only increases the importance of being able to incorporate concurrency in a wide variety of application categories.

In this article we are evaluting a new approach to the concurrency. In the last five years computers are becoming even more parallel. Intel is pushing multi-core achiteture also on commodity personal computers. Neverless the computing power is ofter not well used: one again, hardware is a step head of our day-by-day software development. Remember when the 80286 came into light. The 286 was able to provide a multi-programming architecture but without memory management protection. We had to wait 386 hardware to see software working on preemptive multi-tasking, because software cannot cope with unprotected memory. In one word, it costs too much to develop a operating system without the new features the 80386 bring to us. What about concurrent programming? Can we look similarities in the  concurrency field?

After reading an interesting article on Erlang  and Java interoperability, I have decided to dedicate my spare time to Erlang.

O’Reilly has just published a wonderful book on Erlang, so I decided to dive into it.

Negli ultimi mesi ho sviluppato un motore di ricerca per il codice, chiamato code zauker.

Code Me Mabye

Hey, I just met you, and this is crazy  But here's my number, so call me maybe And all the other boys, try to chase me,  But here's my number, so call me maybe

After a bunch of time, I take back my Erlang Hammer from the sand of time.

Sometimes you are behind a http proxy, and the git:// protocol is not accessible.