And without having this accessible over the network, network transparency goes to Hell.
Again, we're talking about a protocol for a combined compositor/window manager (they merged them, remember?) talking to clients on the local machine. All they are currently making is A.) the Wayland protocol, B.) A combined windowing system and compositor to demo it with and C.) some demo clients. They aren't trying to make some swiss army protocol that magically solves the problems of local displays and remote displays at the same time. They specifically said that's not what they want to do in the first place. Wayland, in any form, couldn't do that and X11 doesn't do it either. If you think that X11 is some kind of godsend then fine, I personally don't care, but they're trying to make something that performs very well locally right now and X11 is mediocre at doing both of those jobs. Just mediocre, and it won't be doing any better in it's current form. Even X11 forwarding, your most cherished toy, slows down horrendously when having to deal with a lot of difficult to compress image data in addition to dealing with input events. I try to drag a rectangular object around inside another window and... what's that? The rectangle can't keep up with the cursor? It's so slow that I might as well just use Spice, a protocol made for remote desktop (and remote desktop alone) network communication instead? My gosh! Who would have thought!
Now, that being said, now that both compositing and window management duty has been combined and simplified, isn't this where you would want to start writing that remote desktop implementation? One that doesn't tie you to tens of years of legacy that forgoes latency hiding and efficiency (Xlib) or one that's so bare metal that you cry every time you look at how much code you've had to write to do anything (XCB)? One that was written for remote desktop sharing in the first place and not a rehash of the same mediocre mess we've been dealing with untangling for years?
VNC operates in terms of the root window, and thus is completely unusable for this purpose. If Wayland developers designed their own remote protocol (even if it was primarily bitmap-based) and window manager interface, it would at least make their efforts somehow legitimate
So if they don't re-invent not only the wheel, but the drive shaft as well, you won't be satisfied? They aren't trying to do the whole job for you. We (the programmers) are supposed to be doing something besides sitting in the peanut gallery and yelling "do more for us! we don't care about your goals!".
-- maybe even add support for X on top of this for compatibility. But now it's "we will draw pretty pictures, dirty people who need remote applications should use VNC!" -- that's completely unacceptable.
Wait, so you missed the part where they're working to run X within Wayland so that you can still run your X applications if you'd like and still be able to use your X11 forwarding if you so pleased? While they aren't building it into the protocol (again, there's no reason they should), isn't that exactly what you just asked for? I know you aren't supposed to read the article here on Slashdot, but I didn't think you'd go so far as to not read up on the topic at all. That is impressive. You've earned your low number.
Exactly. You said nothing at all about what actually triggered the ficticious event you referenced in your fake quote. Not a damn thing. You gave absolutely no context. You just made a vague statement, probably in hopes that nobody would call you on it.
it's not a protocol if you can't use it across the network.
...did you actually say this statement? Wow, never thought I'd hear that. I suppose a sandwich isn't a sandwich if it's not made for eating then? Or doesn't use bread? Please consult a dictionary for that word and get back to me.
And even if it was, there would be still no reason to use it if it is not at least as efficient as X when used for such purpose.
Oh? A protocol and system made for communicating in a low latency environment and relaying large amounts of data around a computer system being slow at communicating over a network? Gosh! Who would have thought. I hear cars don't work well as boats either, even when converted to amphibious vehicles.
There is absolutely no reason for making a WORSE system.
Oh, so you've used this phantom remote desktop system that someone wrote sometime in the future after the desktop portion of it had been completed and actually had some real ground to stand on when evaluating an implementation? Amazing! Can I see it?
You are ignorant. X uses input drivers and its own event system. There wasn't even evdev subsystem for most of the time X existed (and there still isn't on systems other than Linux).
I guess it's a good thing I wasn't talking about X then, huh? The entire paragraph you quoted was about Wayland and Weston. I even mentioned the names of them, would you like me to use blink tags next time? Does Slashdot allow those? If I'm ignorant for actually sticking to a topic without diverging half way through a paragraph, does that make you willfully ignorant since you seem to have intentionally ignored the context?