Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Posted Nov 5, 2010 18:20 UTC (Fri) by drag (guest, #31333)In reply to: Shuttleworth: Unity on Wayland by gmaxwell
Parent article: Shuttleworth: Unity on Wayland
Well you can avoid that just by using software that does not suck.
The only time I want my attention to be stolen from what I am working on is if it's something damn important. Then in those cases I WANT my attention to be stolen.
But really nobody is advocating that we should have constant big swooping animations that do nothing but get between you and what ever text box you happen to be interacting with at the time.
And these animations don't cost you anything really. If you think that having a translucent notification box pop up to tell you received a email is going to take away from whatever your doing your probably very wrong.
Or at least you should be wrong.
We have had hardware around since the late 1990's that is perfectly capable of performing the necessary functions to get what people are trying to get at with things like Unity, Gnome-3, etc etc. Apple's first OS X desktop ran with no GPU acceleration at all!
It's just that graphics suck in Linux. This is what _may_ get fixed if we can break away from the tyranny of proprietary video drivers and everything-we-use-must-be-X.
Posted Nov 5, 2010 18:44 UTC (Fri)
by gmaxwell (guest, #30048)
[Link] (6 responses)
I'm sure that some other people, perhaps most other people, are completely fine with that sort of thing. I wish you luck in creating software for those people to use. Though I am somewhat skeptical that most people actually prefer this sort of thing outside of computers almost nothing else provides indications in that kind of intrusive"interrupt driven" way. (My car doesn't overlay a gigantic oilcan on my windshield when the oil pressure is low it lights up a discrete check engine light and I can attach and OBD tool to find out the cause. When my office paper-mailbox has a letter it's left sticking out where I can see no one copies the letter onto a transparency then slams it in my face)
But even if I really am in the crazy minority here, please don't think that you speak for everyone. You certainly don't speak for me and at least a few other curmudgeons like me and I've been using computers long enough to have a pretty good idea what works for me. That kind of annoyance isn't how I work, it isn't what I want. I put up with this kind of behavior from my computer only in so far as putting up with it is less costly to my time and endurance than maintaining every part of my systems on my own. But as far as I'm concerned a step down from a system that provides no notification at all.
Posted Nov 6, 2010 16:08 UTC (Sat)
by andreashappe (subscriber, #4810)
[Link] (5 responses)
Time to cut back on the hyperboles..
The X-Protocol is currently getting more in the way than helping stuff -- don't take my word for it, Keith Packard's should be enough. There are people trying to improve that: look at the quality of the X stack, they are are a long way ahead from the things that I had to use in the last millenium.
Animations might be added. So what? Scrolling is an animation, tear-free window movement was made possible through that animation work. Who did suffer from that? Wayland might the way forward, but still there's X11 as a possible client to that.
If you don't like it: turn them off. Come on, that would have taken less time than the whining on this forum. So you don't like those transparent popups that disappear after 2-3 seconds and hide the some 8cm^2 in the top right corner of your screen where most of your work seems to happen: disable them. You are able to disable them, some no-clue first-time Linux user surely ain't able to enable them. If you (for some reason) need to install your linux distribution every year automate it. Create a package that does all the magic for you -- other people might even like to use it.
Posted Nov 6, 2010 20:19 UTC (Sat)
by gmaxwell (guest, #30048)
[Link] (4 responses)
I run a distribution in order to outsource basic system maintenance. I have more pressing things to do with my time and I'm willing to tolerate the consequence of system operation that I don't agree with but that doesn't mean that I don't have preferences. I'm speaking up here because I believe that it would be a disservice for me to everyone who has common interests to sit quietly while people pushing features which are harmful to those interests are so vocal.
You make it sound like it's so easy to disable these things. Sadly it is usually not in the interest of "usability" the mere option to disable these things is often completely eliminated or if it remains at all it is deeply hidden (often inside some undiscoverable registry tool). Just because I am more capable than joe-random that doesn't mean my time is less valuable, that I am more patient, or that I am infinitely capable. In cases where the functionality is eliminated patching the software breaks updates and leaves me tracking development, which is the work I was hoping to avoid by using a distribution in the first place.
Going back to the subject that started this sub-thread: If network transparency is abandoned in the GNU/Linux desktop infrastructure I can't simply turn a knob to bring it back! Remote X is functionality I use _every day_. I have three windows open on my laptop right now to a system with a large amount of ram which is able to work on data sets that I can't reasonable work on locally. It works great. And the notion of it only working via shims or with arcane software which I have to maintain myself troubles me greatly.
I'm certainly not opposed to _performance improvements_. By all means, making it faster has my full support. The discussion here was about tossing functionality (which I find critical) in order to enable performance improvements which are mostly inconsequential to me. I am not comforted by the argument that this change is urgently needed due to make improvements like increasingly intrusive animations.
Janne, I must admit that I'm not quite sure if you're trolling me or not but if you are I guess I'm going to fall for it.
Your market share strawman is not well supported by the evidence. Systems with clearly superior user experience have time and time again failed to capture really significant market share (Mac OS for the longest time and even today it's only at perhaps 7%, BeOS, etc).
You're also making the erroneous assumption that I care about having 7% market share (like OSX) vs 2% market share(numbers source). I don't. I care about having a usable _computer_ (as opposed to a home entertainment center, which has large orthogonal usability requirements). I care about having a good option to recommend to other technical people. I care about not having to build my own desktop software stack, even though I would probably be able to create one which met my needs I have other things that I'm working on. While I'd love to see most people running Free software, 7% wouldn't be much of an improvement against the 85% on windows for that purpose... even if I believed that we could solve the marketshare gap with UI improvements.
People use computers for different purposes. Even windows has a small market share if I count televisions and video game systems as "computers". I wonder if we're using 'desktop' market share numbers which are diluted by a great many use cases which would be better served by an appliance? If I were to care about market share I'd want to first care about getting 100% of uses which are best met by powerful computing systems rather than by media players or the like.
I am and I am not alone. And I want a system which is useful for me to run. I also want other people to have systems which are useful for them, even if their needs are different than mine. I feel that non of the major distributions are catering to my interests, and I think thats unfortunate and I hope it changes. The major distributions and major Linux desktop software suites are clearly prioritizing non-technical novice users today. They even say so explicitly. They may be actually failing to satisfy the needs of those users too, but failing to make your target happy isn't equal to having a target which includes other people.
Perhaps animations can play a useful role in a typical user's "next twenty years" but the animations that do probably won't be the same training-wheels animations that you'll create if you're optimizing for the initial impression. I found the example about minimizing to be pretty humorous. Why would I want that? If I care it's because I either don't know what I did, or because I wish I hadn't done it. In either case what I need is an undo button, not an animation. An animation might make it a little easier to manually undo my mistake, but thats really a half-step... We have computers to eliminate manual processes. How many significant usability improvements are we missing because everyone focused on usability is primary focused on newbies and the initial impression?
Posted Nov 6, 2010 21:22 UTC (Sat)
by dlang (guest, #313)
[Link] (3 responses)
it's really hard to put a couple hundred gig of ram into a laptop, but trivial to remote the display from a server that has a couple hundred gig of ram to a laptop that you can carry into a conference room.
you may try to argue that the app could be written to work that way through other means, but that misses the point that with X the app author doesn't have to make a decision of if the app should be network accessable or not. If app authors have to go to extra effort to make their stuff network accessable, most of them won't go to that effort (after all, nobody needs that anyway, that's why the feature was removed from linux systems to start with right?) and the only apps that will have the ability to be networked are the ancient X apps (that predate the change), or high-end 'enterprise' commercial apps where someone is paying for the feature.
this leaves out the huge middle ground where the app author never thought about the need to be networked, but that app ends up being the perfect thing to use when backed by the right hardware. Instead someone will have to fork or recreate the app in a networked version.
Posted Nov 7, 2010 9:31 UTC (Sun)
by roc (subscriber, #30627)
[Link] (2 responses)
Maybe true for simple apps, but complex apps are basically unusable over modest-latency links unless they've been significantly optimized to reduce round-trips to the X server. There are a lot of X APIs that you simply cannot use if you want to be fast over the network.
> this leaves out the huge middle ground where the app author never thought > about the need to be networked, but that app ends up being the perfect
Or just run it under a modern screen-remoting tool.
Posted Nov 9, 2010 2:02 UTC (Tue)
by nix (subscriber, #2304)
[Link] (1 responses)
Posted Nov 9, 2010 6:40 UTC (Tue)
by dlang (guest, #313)
[Link]
Posted Nov 5, 2010 19:30 UTC (Fri)
by dskoll (subscriber, #1630)
[Link] (6 responses)
And these animations don't cost you anything really. If you think that having a translucent notification box pop up to tell you received a email is going to take away from whatever your doing your [sic] probably very wrong.
Are you kidding me? Those notification boxes drive me crazy. There I am, deep in an xterm or an emacs debugging session and some stupid box obscures my text? I want the computer to stay out of my face!
Posted Nov 5, 2010 20:06 UTC (Fri)
by drag (guest, #31333)
[Link] (2 responses)
For example at my current job some of the emails that I get are going to be critical and far more important then anything I would happen to be working on, unless I am working on a emergency... at which time I would have 3 phone lines blazing, people talking over everybody else, etc etc. Then a little pop up in the corner of my window is going to be the last thing on my mind.
In my old job I couldn't care less. There was no communication that mattered enough to be answered right away.
But now I WANT to see that stuff. I WANT to be interrupted. That's a good thing. Because if I get a notification and act fast enough I can stop those above mentioned emergencies. :)
Posted Nov 6, 2010 10:25 UTC (Sat)
by modernjazz (guest, #4185)
[Link]
The problem is there just hasn't been enough effort put into open-source drivers until recently, and the quest for "bling" has really ramped up those efforts. Just like how the commodity/gaming market increased power and decreased the price of computing, for both "serious" and "fluffy" use-cases.
So I'm happy about where things have been going, even though it has made X a pain in the neck for the last couple of years. (Fortunately, it seems to be getting better, at least for me.) But I would bemoan the loss of network transparency in situations where I didn't need the absolute highest-performance graphics.
Posted Nov 11, 2010 17:13 UTC (Thu)
by cdmiller (guest, #2813)
[Link]
Posted Nov 6, 2010 22:31 UTC (Sat)
by Wol (subscriber, #4433)
[Link] (2 responses)
Perfect example. KDE. I have a taskbar at the bottom of my screen that currently says "Konsole (2)" - ie I have two Konsoles (currently hidden). Let's say I put my mouse over it - it now displays what those two consoles are. All fine and dandy - UNTIL I actually want to select the upper of the two.
If I don't know which one I want, or I'm slightly hesitant, or I'm not good at moving my mouse, or or or ... the mouse hovers over the FIRST konsole description a tiny moment too long, and the information popup appears, COMPLETELY obscures the second Konsole button that I actually want, and JUST WON'T GO AWAY until I go back to "Konsole (2)", get rid of the whole damn lot, and have to start ALL OVER AGAIN.
Don't forget - these information popup bars have a habit of following the mouse. In other words, if you're slightly unsteady, or can't aim quite right, or anything else where the mouse is wobbly, there's a damn good chance the popup is going to pick a damn inconvenient place to appear.
Quite why the KDE people chose the place they did for the popup I'm moaning about I do not know - it is INCREDIBLY stupid, but hey, I'm sure they have some very clever people who thought it was a good idea ... :-)
Cheers,
Posted Nov 6, 2010 22:43 UTC (Sat)
by dlang (guest, #313)
[Link]
personally, I choose to have it never group and I set the taskbar to be tall enough to show enough rows to have a useable amount of text in each of the icons.
Posted Nov 7, 2010 1:32 UTC (Sun)
by boog (subscriber, #30882)
[Link]
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
To quote my first message on this thread:
Shuttleworth: Unity on Wayland
Perhaps a distro fork will arise targeting people who are technically competent [and are] more interested in productivity.
Posted Nov 6, 2010 10:22 UTC (Sat) by Janne (guest, #40891)
With attitude like this, it's no wonder that Linux on the desktop is perpetually stuck at under 1% market-share...
People are not computer-wizards.
The computer should do everything in it's power to help the user.
It seems to me that the people carrying the biggest "help people" banner often do the most harm. I too want the computer to help people, even non-technical people. I suspect we have very different ideas of what "help" means. I can assure you that adding more popups and interface interrupting animations will not help _me_ in the slightest. Other folks, perhaps, but I don't intend to speak for anyone else.
And sure, people will learn which button does what. [
] And there are even studies about this. Researchers set up two functionally identical systems. The difference was that one system looked plain and basic, while the other has nice graphics [
]. It was found that people were more productive on the system that looked better.
If you provided citations I would read them. But what concerns me with this is that it seems like an unhealthy obsession with the initial impression. Your first few hours with a system are entirely different than your next twenty years with it. Unless you are worried about every last fraction of a percent of market share I believe you should optimize as much for the 'next twenty years' as is possible without turning people off completely. (For example, I think Blender fails a bit too hard on the initial impression)
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
> be network accessable or not.
> thing to use when backed by the right hardware. Instead someone will have
> to fork or recreate the app in a networked version.
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Shuttleworth: Unity on Wayland
Wol
Shuttleworth: Unity on Wayland
KDE obscuring tool tips