Live data from Hacker News

That’s it, we’re quitting

design.canonical.com

121–130 of 137 posts

Re: That’s it, we’re quitting

#121
post #120

Earlier quoted context omitted.

I've used an iMac that shipped with Snow Leopard and it shipped with a single-button mouse.

Check System Preferences. It’s off by default. Mice that support right clicking have been shipping with every Mac since 2005, trackpads that support right clicking with every Mac since 2006 or so.

> Check System Preferences. It’s off by default.

If it's off by default it doesn't exist for most users.

Re: That’s it, we’re quitting

#122

Getting rid of quit/close requires the user to learn entirely new metaphors every time they use a program in order to know how to get a program to stop taking up resources. In a system with effectively limitless resources this is fine, but in lower specced systems, not so much. Also "effectively limitless" means equivalent to the specs of the worst system the designers use, which will likely skew things. Where I'm si…

As someone who has used Matlab, and someone who has used Eclipse, you can take my "get your fat ass out of RAM already" command when you pry it from my cold, dead fingers.

Nobody is taking xkill or kill -9 away.

Re: That’s it, we’re quitting

#123
post #118

Earlier quoted context omitted.

> It is extremely annoying that this starry eyed experimentation is going on in the most popular Linux distro. They are basically risking the one foothold Linux has been able to make in the desktop world. If you want to experiment, you should start an experimental distro and not risk your's and Linux's one single solid success. That is an excellent point, and one that worries me, too. On the other hand, I'm glad that…

Less Linux-savvy Ubuntu users are less likely to try out a non-mainstream distro/variant. It's hard to find the "best ones" without testing these new features on these users. Sometimes your users are your Guinea pigs. I think Ubuntu will be fine as long as they remain responsive to user feedback and maintain "get me back to what I'm used to" options for experimental features.

Ubuntu/Canonical might have better luck by releasing a more rolling release distro to test these changes. The Daily build is fine and all, but it reflects the status of the trunk. Having a few branches that can go on wild adventures, killing off 'quit' buttons and rearranging the UI, might benefit them more than the cost of implementing it.

I'm specifically referencing the way Fedora tends to be the frontline for RedHat and CentOS updates, and isn't afraid to roll back when things go bad.

Re: That’s it, we’re quitting

#124
post #120

Earlier quoted context omitted.

I've used an iMac that shipped with Snow Leopard and it shipped with a single-button mouse.

Check System Preferences. It’s off by default. Mice that support right clicking have been shipping with every Mac since 2005, trackpads that support right clicking with every Mac since 2006 or so.

So... when I help someone out and need to right click, it's not an annoyance to either alter their settings or have to use two hands? The 'single button interface' demand is silly - all it does is force people to use modifier keys to get the functionality they need. How this is different to just enabling right-click I'll never know.

Re: That’s it, we’re quitting

#125
post #73
post #60

Earlier quoted context omitted.

http://www.apple.com/macosx/lion/ “Say good-bye to manual saving. Auto Save in Mac OS X Lion automatically saves your work — while you work — so you don’t have to. Lion saves changes in the working document instead of creating additional copies, making the best use of available disk space. The lock feature prevents inadvertent changes from being saved and automatically locks documents after two weeks. And the revert…

So instead of "save" which seemed rather simple to me, you have to learn two new features such as "lock" and "revert", which do not seem so simple to me. Oh and also, now you have no idea what data is saved in your documents. Your documents can carry in them hidden past versions without you being aware of it. Which can prove very embarrassing in many business situations. Which means that anyone that handles sensitive…

I think that losing unsaved work is a bigger and more common problem than those downsides you mention. Locking and reverting is not something mandatory, users can simply ignore those features until they need them. On the whole I see automatic saving as a nice step towards computers as an appliance that can be used with less and less regard to implementation details. (The security side is an interesting point, I wonder how they solve it.)

Re: That’s it, we’re quitting

#126
post #106

Earlier quoted context omitted.

So, "drag and drop" out of iPhoto isn't what you want, and you don't want to just use the "open file" dialog from another OSX app (since that lets you access all parts of the iPhoto library), and then you don't like how you have to click down a few folders once you do use "show package contents"? The only person going out of their way to make this difficult is you. FFS, Apple is far from perfect, but the things you'r…

Let's imagine I use a Mac. I open Gmail and I want to send my father a cute picture of his niece. There's no direct way to do this without leaving the application I'm in (Safari) and going somewhere else to get at the picture. By contrast, if this were a Pages document, I could simply click on "Attach a file" and then browse to the folder where the document lives. In the case of iPhoto and iTunes, this feature - file…

> Let's imagine I use a Mac. I open Gmail and I want to send my father a cute picture of his niece. There's no direct way to do this without leaving the application I'm in (Safari) and going somewhere else to get at the picture.

I hope you are not serious, because it's not only trivial, I explained how it works in the comment you first replied to:

> * If you want to open one of your pictures in a third-party software, OSX's standard file picker has a "media" section which gives you a special iPhoto file picker (which works extremely well, it can even search through all your tags and faces)

OSX's standard image picker has a direct access to iPhoto libraries, and gives you direct access to iPhoto's search engine as well. Likewise for iTunes.

> I really don't see how. I want something perfectly normal: I want "Attach a file" to work. In many cases, with many Apple programs, it does. But in a number of other cases (iPhoto, iTunes), it does not. This is not my fault. I am not doing anything special or nerdy or geeky here.

Out of 6 phrases in this comment, only 2 are correct. And one of them only barely.

Re: That’s it, we’re quitting

#127

Earlier quoted context omitted.

> I remember the program automatically copying the files from a camera to some folder deep within the hard drive and then giving not a clue later as to which folder that was and certainly not allowing any exploration between folders... Well the fundamental idea behind iPhoto is: why would you care where it put your files at all? * If you want to see or edit your pictures, you can do so via iPhoto (or iPhoto-compatibl…

> Well the fundamental idea behind iPhoto is: why would you care where it put your files at all? As you say, it's not just iPhoto - it's a big part of the iVillage. Certainly some people - not just geeks - like this approach, but I find it patronizing ("Don't worry your pretty little head about where we store the files.") and authoritarian ("You may not delete the Pictures folder from your home folder or give it an a…

"Don't worry your pretty little head about where we store the files."

It's just a different type/style of abstraction that may not be suited to you!

All file systems essentially hide the nasty details of where and how files are stored (which inode does it start at, is it fragmented across multiple sectors, which physical device?).

From a UX point of view there is a lot to be said for not treating every single file in exactly the same way.

I'm sure it's an approach that will get more and more prevalent in future (context relevant functionality for the types of files you're currently interacting with/managing).

Re: That’s it, we’re quitting

#128
post #98

Earlier quoted context omitted.

I agree, generally. I find Mac the most irritating platform to use -- the shortcuts are all different because Apple has a silly insistence of using Super where they should use Ctrl, and common shortcuts are supplanted by the OS, leaving apps to have to find new ones. The Dock is a slow method of switching and Sup+~ shortcut to switch to a windows is more annoying than a straight Alt+Tab. Sup+H and your window goes aw…

Actually, Apple's use of the Command key for GUI shortcuts both precedes the use of Ctrl for the same task and pioneered many of the conventions, such as Ctrl/Cmd x, v, c & s, that are universal today. Although I was a bit skeptical at first, once I got used to the concept it made a lot of sense. On a Mac, Ctrl+key combos are for contextual menus in the GUI and navigation/commands in terminals and text areas. For ins…

My apologies for the formatting being messed up, I forgot that the * character invoked italic formatting. That last sentence was supposed to be a footnote.

Re: That’s it, we’re quitting

#129
post #32

Getting rid of quit/close requires the user to learn entirely new metaphors every time they use a program in order to know how to get a program to stop taking up resources. In a system with effectively limitless resources this is fine, but in lower specced systems, not so much. Also "effectively limitless" means equivalent to the specs of the worst system the designers use, which will likely skew things. Where I'm si…

ahem, in mobile we do not have quit..nothing broke not even the mobile users :)

... to its detriment, at times. I have a very good app on my iPhone that plots out bike paths around London for me. Sadly, when I have reached my destination, and "close" the window, it continues to use the GPS and other battery sucking things to the point where I have to manually go and kill it via the kill-menu (which is all I ever use the fast-switch menu for).

I'm not saying this is Apple's fault, but that it's very hard to work out when someone has "finished" with an app that could continue to, say, provide information about what the user is doing to a third party, or sucking battery life, or making annoying noises, for example. And apps that do this after I'm "finished" with them annoy me to no end. I'd consider that "broken" :)

Re: That’s it, we’re quitting

#130
post #120

Earlier quoted context omitted.

Check System Preferences. It’s off by default. Mice that support right clicking have been shipping with every Mac since 2005, trackpads that support right clicking with every Mac since 2006 or so.

> Check System Preferences. It’s off by default. If it's off by default it doesn't exist for most users.

You were completely wrong and I corrected you. That’s it. I was not commenting on the wiseness of not enabling the right click by default.
Post reply on HN