azz:
Red Hat's (and, more generally, Xorg)'s take on the XGL mess.
This looks like a far more sensible approach -- add an extension to the existing X server so that you can do OpenGL rendering the way you're meant to do it ("indirect rendering").
I still don't really see the point of whizzy OpenGL effects on the desktop, but accelerated indirect rendering is something I'm entirely behind, since it'll mean that I can use OpenGL apps over a remote X connection and still get reasonable performance -- something I was doing with SGI hardware in 1999.
azz:
"Blue items have been developed by S60 as part of the browser that is delivered to S60 licensees. Code in the blue items is not currently contributed to open source."
So, in fact, it's not OSS at all.
David: To be fair, it does take advantage of^W^W^Wexploit OSS.
azz: Yes, but only in the same way that, say, Internet Explorer does. ;)
David: Exactly :D
azz: "curn is an RSS reader. It scans a configured set of URLs, each one representing an RSS feed, and summarizes the results."
"rawdog, a Python-based RSS reader, is similar to curn, in spirit, features and invocation. I had no idea rawdog existed when I wrote curn."
He's not kidding -- curn and rawdog are virtually identical! It'd be pretty easy to write a tool to convert between their config files and template formats.
I hadn't heard of curn either until I spotted it in my Referer logs just now.
I guess there really aren't very many different ways to design an RSS reader. :)
Aside from the implementation languages, I think the major differences are: curn has better documentation, and rawdog's plugin mechanism is more flexible (since curn only lets you write output plugins).
I do like the SaveAs feature curn's got; I might have to add that to rawdog at some point...