Why we maintain desktop apps for OS X, Windows, and a web application

Post by hyperion2010 » Fri, Jul 10, 2015, 4:29 PM UTC

pknight wrote: post #73

hyperion2010 wrote: post #52

The alt-tab argument is a strong reminder for me that as good as tabbed browsing is compared to the old IE6 hell, tabs are an absolutely shit paradigm for window management, better than the windows task bar when you have 100 tabs open, but it is about time someone sat down and did real and serious UI research on how to deal with having 100s of windows open at the same time, because my solution of having 32 virtual de…

are you using Windows 10? I'm wondering if the virtual desktops feature was going to make my life easier managing tons of windows. Your comment doesn't sound very encouraging.

Post by jfb » Fri, Jul 10, 2015, 9:34 PM UTC

mosburger wrote: post #83

jfb wrote: post #32

Earlier quoted context omitted.

I use the Fluid SSB [1] for the latter. It sandboxes websites that I need to use but are not willing to allow access to my primary browser history/cookie store. It's a little clunky, but it gets the job mostly done. [1] http://fluidapp.com

I love fluid because of the thing the article mentions about Alt/Cmd + Tab... it's hard-wired into my brain to mean "task switch", so I have several web apps that I use all the time (GCal, Pivotal Tracker, Asana to name a few) with Fluid apps so I can quickly change to them.

Post by BillinghamJ » Wed, Jul 22, 2015, 7:32 AM UTC

hollerith wrote: post #92

BillinghamJ wrote: post #79

Earlier quoted context omitted.

No. I said it "may well be", because a naive implementation using a native language may block while doing IO and be less responsive, unable to do other things while waiting for external stuff to happen. Perhaps I should have said "may well be more responsive than".

So, you don't actually know anything about whether native apps block on IO? (I doubt they do on any modern version of Windows, OS X, Linux, Android, iOS or Windows Phone.)