The whole GGI/KGI spat
"Brian S. Julin" <[email protected]>
| Newsgroups | gmane.comp.xfree86.forum |
|---|---|
| Message-ID | <[email protected]> |
I've been trying to avoid actually posting because it drains time from coding; I'll keep this short. First I'd like to ask folks to please calm down and concentrate on finding points of unity that everyone can agree on. Also, even if there has been too much damage done in the past and the present threads on the subject for X people to feel inclined to work towards at least running on GGI or KGI, both sides can learn a lot from the other, *if* the criticisms are kept constructive. By constructive, I mean point out how the other side could make non-invasive improvements that increase the usefulness of the communal codebase. I don't think there are many people here that do not realize that modularity and reusability of code are desirable traits. It's pretty well accepted by and large. Also I don't think there are many here that do not realize that in order to milk hardware for what it is worth, X needs much more thorough kernel-space support than currently provided by DRI. This could come as a result of improving DRI, starting something new, or developing KGI to the point where it can satisfy X's needs, but in the end, it has to get *done*. Finally, both sides can level criticism at each other about how they "go to far" and entangle things that they don't need to be playing with. Both sides are right in that fight, that's not the question. The question is, how do we fix it? As an example, consider GII. This is a under-rated concept that could sure use the love and care it deserves, and has the potential to either act as a source for code for, or itself be morphed, into something really incredibly useful (not that it isn't pretty useful already.) Doing so would releive the X community from having to support that section of their codebase -- all the mouse protocols, internal keymapping mess, and OS-level nuances could be worked on by a group that includes both people who don't like X, and people who don't like the graphics portion of GGI. Even people who don't like either. The difference here is that they would be working together in spite of this fact. OK, so that sounded way band-campish, and I am picking at the low hanging fruit admittedly. But you get the picture. Please lets try to get something more out of this conversation than elevated stress levels. -- Brian S. Julin GGI and KGI Projects