Frontiers: A New Xlib Compatible Window System
alucard writes "The JourneyOS people have published this overview of their upcoming window system. It looks like it is OpenGL based and uses XML as the communications protocol. The biggest news is that it is supposed to have Xlib compatibility, but uses HyperQueues instead of Unix domain sockets. Could this get rid of the speed problems of XFree86 while still retaining Xlib compatibility? I think this is something everyone wants, but projects to create alternative GUIs such as Fresco and PicoGUI have given up any hope of compatibility with X11 or Xlib. Can we expect another alternative out there soon?"
"BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
emacs vs vi and gnome vs kde flamewars are getting old, we NEED a new one.
Be wary of any facts that confirm your opinion.
I suppose a gimp can run faster than Carl Lewis, but it'll take an awful lot to train him...
To train Carl Lewis?
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
Actually it goes like this:
Everybody has got to invent their own wheel once, and when they realize how big amount of work is needed,
they never finish it. This is when they might join some existing wheel-building-project.
Sounds great... but do you have a catchy name for it? And a project homepage. Your project needs a cool homepage with lots of screenshots and FAQs and tutorials and download pages and all that. You should do all that to show that you care about your users, you care about getting linux on the desktop, and if you don't I refuse to take you seriously. So there.
>Why is it doubtful that the kernel comes into play?
Because BeOs proponents usually talked about their GUI subsystem, or the multithreaded design of their apps, not of their kernel, that's why I don't think that the kernel
>- Interactive patches (preempt, ll, et al)
I installed the intertactive patches on the 2.4 kernel and I didn't see any difference in the responsiveness of the applications.
>- IP QoS
Uh? We're talking about the responsiveness of X locally..
So IP has nothing to do with it..
Beside as we're talking about X, X is not ideal for remote connections, I believe that a higher level protocol with more things done in the server would be more responsive and use less bandwith..