Comment Re:Welcome to the real world, Kas. (Score 1) 477
Real world, my ass. Yes, it takes applications time to load. Bring up a Microsoft Office product, and that load time is pretty long. But the interface comes up immediately (thanks, no doubt, to Microsoft's unique relationship with their OS).
My cell phone is an ancient, slow turd, but when I start it up, I can access the interface almost immediately, and the log on to the network is extremely fast. Only after that does it start doing things like preparing the indices of SMS and similar stuff.
"The cloud" may not be the answer in this case, but the problem is clear: there are two ways of loading a program. The easy way (for programmers) is to throw up a splash screen, load everything, and then give the user control (as in your Angry Birds example). The right way (for usability) is to get the interface up, and keep loading. It'll usually take the user a while to get "under speed" as well, so why not use that time to load up the bloat?
When someone in an office starts an application, that person wants to work on that application. Two minutes to load, every day, across a whole industry amount to more than enough billable hours to pay for optimization. Applying patches and updates at startup (or asking, "Do you want to start now, or wait 15 minutes while I patch in some completely unintelligible and probably irrelevant upgrade?") is also, in most cases, wrong. It's like telling someone at the McD's drive-thru: "Would you like to wait 15 minutes so we can deliver the same food in a bag that is 5% less likely to tear open?"
3. That's not relevant here, as the post by the Adobe employee was about load times, not EULAs, and it was not a post that portrayed Adobe positively. Besides, Adobe Flash's startup EULAs are worse.
4. If it's fast enough, you won't need a splash, or you won't care. MS Office has splash screens, but I only see them briefly. Photoshop, on the other hand, does nothing for about a minute, then writes over the middle of screen (might even steal the focus) a splash that lasts another minute. I am not impressed.
There's a lot of improvement that has to be done in interface terms, and saying "that's the way programs are" misses the point and affirms what need not be affirmed. Certainly, there are conceivable instances when long, bloated load times are required, but I suspect they're far fewer than the number of programs that are written for the benefit of programmers, and not for the users. Otherwise, why would my tools keep interrupting me?
My cell phone is an ancient, slow turd, but when I start it up, I can access the interface almost immediately, and the log on to the network is extremely fast. Only after that does it start doing things like preparing the indices of SMS and similar stuff.
"The cloud" may not be the answer in this case, but the problem is clear: there are two ways of loading a program. The easy way (for programmers) is to throw up a splash screen, load everything, and then give the user control (as in your Angry Birds example). The right way (for usability) is to get the interface up, and keep loading. It'll usually take the user a while to get "under speed" as well, so why not use that time to load up the bloat?
When someone in an office starts an application, that person wants to work on that application. Two minutes to load, every day, across a whole industry amount to more than enough billable hours to pay for optimization. Applying patches and updates at startup (or asking, "Do you want to start now, or wait 15 minutes while I patch in some completely unintelligible and probably irrelevant upgrade?") is also, in most cases, wrong. It's like telling someone at the McD's drive-thru: "Would you like to wait 15 minutes so we can deliver the same food in a bag that is 5% less likely to tear open?"
3. That's not relevant here, as the post by the Adobe employee was about load times, not EULAs, and it was not a post that portrayed Adobe positively. Besides, Adobe Flash's startup EULAs are worse.
4. If it's fast enough, you won't need a splash, or you won't care. MS Office has splash screens, but I only see them briefly. Photoshop, on the other hand, does nothing for about a minute, then writes over the middle of screen (might even steal the focus) a splash that lasts another minute. I am not impressed.
There's a lot of improvement that has to be done in interface terms, and saying "that's the way programs are" misses the point and affirms what need not be affirmed. Certainly, there are conceivable instances when long, bloated load times are required, but I suspect they're far fewer than the number of programs that are written for the benefit of programmers, and not for the users. Otherwise, why would my tools keep interrupting me?