Senior Member
It is not dead (see Nintendo's latest Wii U console) but the applications have changed.Originally Posted by Cyberax
Senior Member
Many people here are calling Wayland 'immature' - for the current state of Wayland, that may indeed be true. But it will still take a couple of years of development before any mainline distro will start to use Wayland. I am sure that Wayland will be greatly improved in the following years.
Senior Member
Ahem, the only drivers supporting the new kwin approach by using OpenGL ES is the oss drivers. Neither of the proprietary drivers support OpenGL ES properly in order to run kwin. So your above statement is wrong. I just tried kwin with r600g with kwin using OpenGL ES and the performance is incredible fast (this is with stable mesa 7.11). It is much faster than Catalyst with/without OpenGL 2.0 shaders.
AFAIK if you are using nouveau, you have to use mesa GIT.
Senior Member
As far as examples go, that's kind of a different case. The Wii U pad thingy is not a separate device with its own OS and application stack and environment. It's really just another LCD that's attached to the console, except it's 'attached' wirelessly instead of via a display cable.
Now, if the Wii U pad had its own small OS and its own GPU and the Wii U was just sending rendering commands to the pad, then it would be a good example of server-side rendering in the context of X11.
D-Bus does not use XML for its actual IPC, at all. It allows service descriptions to be written in XML, which can be queried _if_ an application wants it, but that's really only good for debugging. You don't query a service description at runtime because getting a random list of methods does absolutely nothing usful for the software: all it cares about is whether the other end implements a specific well-defined previously agreed upon interface or not, which is not queried via XML. When D-Bus does serve that XML, it is basically just blitting it into the network buffer, and not processing it. D-Bus also uses XML for its configuration and automatic startup config, but these are read once upon startup (or when changed) and no XML processing is going on during message transmission. The actual messages sent over DBUS are a fairly efficient binary format.
This is wrong on several levels. First, Windows _is_ just as secure as its user. It's quite possible to have run Windows XP for years with no anti-virus and never haven gotten a virus. The trick is to not download and run OMG_CELEB_BOOBIES.EXE. It's a subtle, difficult thing to master. The same kinds of users who would fail to realize the inherent danger in such an activity, however, are going to be just as stupid in Linux, and when they see a page that says "OMG CELEB BOOBIES, DOWNLOAD THIS AND TYPE SUDO INSTALL_BOOBIES.SH TO INSTALL BOOBIES ON YOUR DESKTOP" they will gladly do that very thing and think nothing of entering their password ("why is linux so lame and asking for passwords all the time? so dumb. just annoying like windows 7 and its uac prompts always asking me if im sure if I want boobies on my desktop! and why is firefox so slow lately anyway?!").
Windows Vista/7 especially are quite secure. I will steadfastly hold to the claim that they are in fact more secure desktop OSes than Linux+X11 by a long shot. That is due to a significant effort put into very fine-grained privilege separation in services, the UAC dialogs and the security of how those are implemented (where's the "please make sure this full-screen window that may or may not be my screensaver unlock dialog really is my screensaver and not something else?" for X11 at?), the significantly more thoroughly protected file system, etc. Sure, it won't ask for a password, but if you actually think about this with any level of critical cognition, why would you care about a password prompt rather than UAC? Nobody but the physical user sitting in front of the machine can agree to a UAC prompt, while on Linux/X11 pretty much anything and everything can snoop on half your password dialogs (did you just put in your SSH key in that root-owned dialog? who cares, any app can snoop on the X11 events to that window trivially, because nobody is actually using XACE for anything useful yet) and respond to password dialogs on their own. Honestly asking a user to type a password does not protect him from malware any more than clicking a properly protected button does, because either one requires the user to consciously decide to do something stupid. The whole purpose of such things is to verify the human's intent, and the Windows implementation actually succeeds at that while the Linux implementations do not.
Password prompts are built around the assumption that someone else is physically at your computer trying to mess it up; let me tell you, if someone is physically at my desktop, they've already broken into my house and I have bigger problems than my PC; and if someone got into my laptop, that means they already got past one password prompt at the login/unlock screen and clearly a second password prompt is not going to deter them further. Linux is just obnoxious when it even tries to be secure, while Windows is effective and as unobtrusive as possible.
The Linux desktop has things to learn and emulate from the modern Windows experience. Laughing at something you obviously haven't used or understood while trumping up the out-moded and poorly-conceived UNIX tradition of password prompts is not helping you, Linux, or anyone else to be more secure and safe.
Senior Member
not related to wayland but after reading elanthis post i stumbled uppon this:
http://venturebeat.com/2011/08/05/wt...rity-approach/
this comes from a guy that was hired to tackle the security problems in Win.
Reply With Quote
