The way I read it is that they want other operating systems to adopt the same infrastructure, e.g. kernel mode setting, instead of implementing an abstraction layer in Wayland itself.
If winlogon runs in the same security context and the same desktop as explorer.exe then a key logger will be able to intercept all logins, and a screenshotter will be able to take screenshots of your login screen. Clearly you don't want that to be possible.
Or are you saying that they never should have made Ctrl-Alt-Del do anything else but starting the task manager?
I'm not the guy who voted you down, but I'm guessing other people did it because your posts' attitude imply that new users are absolutely not worth accommodating for and that usability is not important. It comes over as rather elitist.
Your posts remind me of typical Linux-on-the-desktop-defending posts that claim Linux's usability is just fine. Making X.org work isn't difficult, just run these 4 incomprehensible commands, edit this configuration file and insert this snippet for which you have to read a 50 page manual to understand. It's easy! What, can't do it? Then you're not deserving to use Linux, but Linux is oh so user friendly! (disclaimer: I love Linux, I want it to succeed on the desktop, but this kind of attitude is helping neither Linux nor Git)
I haven't used RedHat-based distros for years now but I remember that back when I switched to Debian-based distros I was equally confused about Debian's package management system. I didn't think, and still don't think, that dpkg and apt are documented that well. To answer your question: yum is to rpm as apt is to dpkg. But I've always found it weird that there's a difference between apt-get and apt-cache; in contrast, "yum install" and "yum search" use the same executable. The documentation concerning building Debian packages is often out of date and scattered all over the Internet with no clear central place. And finally there's this "aptitude" thing; I still don't understand why it exists and how it's different from regular apt.
This is actually a pretty good idea. The captcha should include some kind of system for reporting slavery or other kinds of work-related abuse, whereby the reporter will be rewarded if the report results in the slavedriver being successfully prosecuted. As the number of employees become bigger, the likelihood that at least one of the employees will rat out his employer increases exponentially.
There are a lot of local root exploits in Linux the past few years. But ever since Linux dropped the stable-unstable version numbering scheme, different distributions ship a wide variety of kernels + their own patches instead of "the latest kernel" because the latest may not necessarily be stable. How do I find out which local root exploits my distribution's kernel is vulnerable against, and how do I find out how quickly they get fixed? I'm on Debian 6 right now.
I keep hearing this battery life thing but how much battery life does H264 hardware acceleration really save? I dare to wager that the majority of the power is used by the screen, not the CPU.
The sections are really short. Giving each section its own URL will make the reading experience horrible. Most of my users told me that they actually prefer a one-page manual because it makes searching easier.
The thread identifier is not the problem. I'm only displaying one comment topic at a time by using a lightbox. However once I have loaded a Disqus comment topic, switching to another one seems to fail randomly even if I call their documented DISQUS.reset API.
If people keep repeating the same thing then that would qualify as an active discussion. Juvia is specifically not designed for active discussion. It's just for simple commenting.
Yes. Still working on it though: https://github.com/FooBarWidget/mizuho
It's not finished yet. The Juvia site key and URL are currently hardcoded in the source.