Often I am getting into discussions between the differences and the overlap between Chromium and Equalizer. Just recently I had an email conversation with one of the Chromium contributers about the comparison on the Equalizer website. The point of this post is to get your feedback and input to make this page easier to understand and more balanced.
Admittedly, the page simplified things quite a bit. I tried to keep things simple in order to make the main differences clear. On the other hand, this was unfair for Chromium, since it failed to mention it’s parallel programming aspect. I have updated the page already, but now it is no longer simple.
My opinion is that most of the time Chromium is used and perceived as a tool to run unmodified application in a one-to-may display wall configuration. The parallel extensions (composition and OpenGL synchronization) are helpful when developing parallel applications, but don’t go far enough.
Personally I think that Equalizer addresses more of the common problems for parallel OpenGL applications (configuration, synchronization, network distribution) and is the better tool for developing a parallel application. On the other hand, Chromium is an excellent tool to run unmodified OpenGL applications on large-scale display walls, as demonstrated at WWDC’07.
So – what do you think and what would you change on the comparison page? Are there other arguments you see for Chromium or Equalizer? Please leave a comment and I’ll reply.