So, I see this as rationalization.

The fact is, you took a leadership position, and later turned your coat for reasons that perhaps made sense to you. But they don't really make sense to anyone else. So, yes, everyone who supported you then is going to feel burned.

You also made yourself a paid voice that was often hostile to Free Software, all the way back to the SCO issue. Anyone could have told you that was bound to be a losing side and you would be forever tarred with their brush.

So nobody is going to believe you had any reason but cash, whatever rationalization you cook up after the fact. So, the bottom line is that you joined a list of people who we're never going to be able to trust or put the slightest amount of credibility in.

And ultimately it was for nothing. I've consistently tried to take the high road and it's led to a pretty good income, I would hazard a guess better than yours, not just being able to feel good about myself.

Meh, it's easy to find people with skill. With values, OTOH...

You have a point.

Great. Name calling, with zero actual substance. I am reminded now why I don't frequent Slashdot much anymore. I suppose you can't be bothered to bring actual arguments against what I wrote in my earlier, post, right? No, spitting out curses is much easier of course. It should be completely obvious that I am *not* speaking for Raster, but instead am stating that he *would* agree with what I said since his design decisions for Evas are pretty much what I described. But hey, I don't expect an actual discussion anymore. Continue with your infantile name calling.

If you mean enlightenment evas, note that the lead developer would agree with me. Evas has been one of the earlierst adopters of client-side drawing. It is so efficient that it can even outperform GL-accelerated 2D drawing in certain cases. Evas has (or had) support for the Xrender extension as well, but quickly dropped that, because letting the application handle all of the drawing and small-bitmap blitting (by that I mean stuff like icons) is so much more efficient. If anything, Evas is a perfect example of why the "blitting bitmaps" paradigm is the better one.

And none of them use the X way of remote desktop either. Yet, they are efficient, and in heavy use. You make it sound as if remote desktop is unfeasible without the X remote functionality, which simply isn't true. Stick VNC/RDP to Wayland, and you are done.

Again, I wrote:

Also, you completely disregard the MUCH bigger number of administrators and helpdesk personnel working with VNC, RDP, Citrix etc.

You said it yourself: the X remote functionality is okay for *old* stuff (RHEL5 is from when, 2007?), which still draws content by asking X draw this line, that text etc. It is much more efficient to let the application draw these things by itself these days, which is why every newer toolkit and application uses this client-side drawing model. And this is *exactly* where X is broken: it is fundamentally ill-suited for this new paradigm, which only needs a much simpler system. One like Wayland, which only provides surfaces applications can draw into. That's it. Anything else is an anachronism.

Qt4 just pushes bitmaps (even Qt3 did, partially). So does Gtk 3. So do Chromium and Firefox, and IIRC also Thunderbird. Yes, that fits the term "most", unless you are running some old distro.

Which is what 99,99% percent of all modern OpenGL applications will do.

You are talking about indirect 3D rendering, which is a fundamentally different topic. It is true that you can in theory send OpenGL command streams over a network, but in practice, this works only for certain applications, where the size of the commands is not too large, and no large assets (textures, meshes) etc. are transmitted. There's a reason why everybody wants *direct* rendering for 3D on the local machine. Forget about running games with indirect rendering, for example.

But when it comes to 2D applications, it quickly becomes obvious that the X protocol is useless nowadays, since most application draw paths, fonts etc. on their own, and X only gets to handle window-sized pixmaps. X drawing commands are almost never used anymore, except by some ancient stuff, like xterm. In that case, that fancy "X11 transparency" will end up transmitting raw bitmaps over the wire. Just use RDP, VNC etc. instead.