I used to not be busy. I used to be in school. Things were easy then. I could blow off classes and just hang out in the the computer lab, coding.
But, the fact that I'm wasting away my arms typing all day for money doesn't lessen my need to write my own code -- stuff that I can call my own, and give away. So, I've been working on several projects here at home, on my days off or when I get home and don't feel like sleeping.
Another thing that makes Y a much better (in my opinion) solution is that clients running on the same machine as the server (or in Y, the "microserver") do all the drawing themselves. All necessary window state is kept in shared memory and clients make calls through various vtables that end up dealing with the display memory itself, after locking the appropriate window-level semaphore. So, you don't have to worry about all the context switches and serialization of drawing requests imposed on you by the X server.
The Display, Window, and GC object currently have two vtables available to them. One is the local vtable (which corresponds to a client rendering directly to the hardware) and one is the network vtable, which packages up stuff and ships it across the net to the network server, which is itself another Y client, but one that uses the local vtable.
Oh, and it's not pronounced "why", it's pronounced "oo". It's not actually an english character at all. It's cyrillic (but I don't have a cyrillic font)...
I'm probably going to start putting up work-in-progress type tar files up on the hungry site (and actually make web pages for these things), but until then if you're interested (or on the offchance you'd like to help) just send me mail and I'll tar up my tree and ship it off to you.