Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

That’s it, we’re quitting

design.canonical.com

Post reply on HN
Print view View original

1–10 of 137 posts

Re: That’s it, we’re quitting

#2

Post by bmelton »

I'm certainly impressed that the Canonical team are thinking about UI issues in this much depth. It is admittedly FAR more thought than I've ever given to the 'Quit' command, ever.

And while my initial thought is that there are much more important UI/UX issues to be solved in Ubuntu before this, I think that thinking of things like this are key in fixing the global UI altogether.

I'm not entirely certain of whether or not this is the best suggestion though. I LIKE to quit applications. I like knowing that they aren't running in the background, that they aren't consuming resources, that they aren't going to pop up a notification, that they aren't cluttering up my taskbar. I'm the same way with browser tabs -- I don't like having any more open than I need.

If I'm in the middle of something, and need to have a lot of tabs open, I'll generally open a new browser for my casual browsing that I can close when I'm finished. Conversely, I almost always keep Photoshop open, even if it's idle, because launching it takes more than a couple of seconds. I don't know if getting rid of quit is exactly what I'm looking for.

Re: That’s it, we’re quitting

#6

Post by gm »

This argument is pointless. The argument makes no sense without putting in the context of content creation vs content consumption.

Content creation is very resource incentive. If you don't quit any apps ever, you run out of resources. Simple as that.

Content consumption, on the other hand is easy and very optimized. Always have your browser running with 10 pages loaded at the same time you have your music player running and have a movie paused. No problem. Never quit anything.

Then the argument starts to make some sense.

Re: That’s it, we’re quitting

#7

Post by alextp »

gm wrote: post #6

This argument is pointless. The argument makes no sense without putting in the context of content creation vs content consumption. Content creation is very resource incentive. If you don't quit any apps ever, you run out of resources. Simple as that. Content consumption, on the other hand is easy and very optimized. Always have your browser running with 10 pages loaded at the same time you have your music player runn…

It's not about never quitting, though. It's about quitting when you close the last document, or something similar, and breaking the distinction between closing and quitting.

Heavy-duty apps should quit in the background after you close what you were working on, but this shouldn't necessarily matter to the user.

Re: That’s it, we’re quitting

#9

Post by zacharypinter »

alextp wrote: post #7
gm wrote: post #6

This argument is pointless. The argument makes no sense without putting in the context of content creation vs content consumption. Content creation is very resource incentive. If you don't quit any apps ever, you run out of resources. Simple as that. Content consumption, on the other hand is easy and very optimized. Always have your browser running with 10 pages loaded at the same time you have your music player runn…

It's not about never quitting, though. It's about quitting when you close the last document, or something similar, and breaking the distinction between closing and quitting. Heavy-duty apps should quit in the background after you close what you were working on, but this shouldn't necessarily matter to the user.

Right, or go into some sort of tombstoned mode when resources are needed and the app hasn't been in the foreground for a while.
Post reply on HN