News for hackers. Stuff that matters.
Re:Splash screens == sloth by JS_startup on Monday February 20, 2012 @10:08AM (#3612577)
I don't understand what he's angry about. Photoshop, Microsoft Office, OpenOffice, these are all enormously complicated programs that require resources to load. That doesn't make them bloatware and it doesn't make the programmers lazy.

His proposed solution sucks too. Show the UI while it's loading so the user can impotently click around waiting for the program to "turn on". Windows does this when it boots up and it drives me insane -- if the OS or program isn't in a usable state when you show it to me, don't show it to me

Loading speed is just one of a multitude of factors that come into play when making software. According to this Adobe employee it should be the chief most concern, even dominating other things like features, usability, UX, cost, technological debt, etc.

Re:Splash screens == sloth by powertower on Monday February 20, 2012 @10:54AM (#3612730)
Sounds to me like he's either temporarily enraged, or is trying to get fired.

The spashscreen does 1 thing, it tells the user that the app is loading and you don't need to click the exe/icon again.

His solution to a 5-10 second load time is to provide a fake UI, record phantom mouse clicks, and also give the user a game to play, only makes everything worse.

Some apps have to initialize, and without that you are left with an empty shell of a UI that has no functionality. Or even worse, a slugish UI that initializes in-place or during work... Which then causes the typical user to go online and rant about how his app is broken or unresponsive.

Though I like what he has posted on the rest of his blog... http://asserttrue.blogspot.com/

Re:Splash screens == sloth by kzrdude on Monday February 20, 2012 @05:05PM (#3614154)
> The spashscreen does 1 thing, it tells the user that the app is loading and you don't need to click the exe/icon again.

This is the wrong way to notify. Let its dock icon bounce on (or similar), instead of obscuring the center of the working area on the computer.

Re:Splash screens == sloth by LoneWolf on Monday February 20, 2012 @09:47PM (#3614996)
Excuse me but I don't see that being possible in Windows In kde it was mac I have no idea but your solution only works in some places.
Re:Splash screens == sloth by derefr on Tuesday February 21, 2012 @03:18AM (#3615697)
Then that is a problem with the GUI, not a problem with the program. Don't settle for what's possible; change what's possible.
Re:Splash screens == sloth by wmil on Tuesday February 21, 2012 @12:38AM (#3615352)
Adobe has been laying people off, he could be trying to draw attention to himself in order to find a new job.

Anyways he's solving the wrong problem. What he really wants is to have the OS log him in, lock the screen, and load his common apps before he gets to work.

Re:Splash screens == sloth by tintin on Monday February 20, 2012 @10:21AM (#3612627)
You are wrong.

Everytime I start Blender (3D content creation suite) I'm blown away by the time it takes to start. Less than 2 seconds! Ready to use!

Do I call Blender a complicates program? Yes I do. The feature list can compete with the one of 3ds Max.

Re:Splash screens == sloth by talmand on Monday February 20, 2012 @10:40AM (#3612686)
I think it's unfair for you to call him wrong, what's wrong with what he said in the context of what he was saying?

I remember Blender loading fast as well. But are you sure every single feature of the program is available as soon as the GUI is displayed? Because I wouldn't be surprised if there's some lazy loading going on. Maybe some things finish loading in the background so they are not available right away or maybe some things are loaded on demand to spread out the loading time.

Re:Splash screens == sloth by jakejake on Monday February 20, 2012 @01:22PM (#3613284)
I remember one of the versions of PhotoShop (perhaps it was CS2) no longer loaded fonts at startup and the launch speed improved. But then the first time you select the font drop-down you had to wait around 5 seconds.

So I guess the launch was faster but waiting for the fonts to load was annoying when I was in the middle of working. During the app startup I'm probably spacing out for a few seconds while the app launches.

I see similar things in other apps. One that comes to mind at the moment is Eclipse where there are certain menu items when you drag over them the app freezes for a second. I always curse myself when I accidentally roll over one of those.

Particular parts of the app that require a lot of disk access may have a bit of a performance hit and so it makes sense to lazy load them, but it is a trade-off and sometimes I'd rather just wait a few moments at launch instead of getting killed by a thousand cuts while working.

Re:Splash screens == sloth by talmand on Monday February 20, 2012 @01:50PM (#3613371)
That is exactly the debate between loading upfront and loading on demand. Either way, you'll have to load resources. But it seems sometimes people like to ignore that fact. The key is finding what works best for the particular application at hand. Personally, for something like Photoshop I'd rather have the long upfront load as opposed to hitches when loading a feature on demand.

Which, out of curiosity I timed it, the "long" loading time for Photoshop CS5 on my machine is less than six seconds. It think I can wait that long.

Re:Splash screens == sloth by masklinn on Monday February 20, 2012 @04:00PM (#3613897)
> That is exactly the debate between loading upfront and loading on demand. Either way, you'll have to load resources.

Everybody seems to be missing the third way: load in the background as the user can already work.

Take those fonts, you could spend 5s loading them during the splashscreen making the user wait, you could spend 5s loading them when first requested making the user wait again. Or you could load them after the program has started, in the background.

Will the user go from "empty document" to opening the fonts dropdown in under 5s? Pretty damn unlikely, and if he does he'll wait for the remainder of the load. In either case, he just "won" 5s.

Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @11:23PM (#3615212)
Problem then is that as soon as I start using the program I might say want to load some data into it which is on the same drive as the program itself.

If I don't have an SSD my drive head is going to be spinning around like crazy trying to load resources from different parts of the disk at once which is going to give me slower overall performance. If you do have an SSD then it's likely fast enough either way.

Re:Splash screens == sloth by sixothree on Monday February 20, 2012 @03:49PM (#3613853)
Eclipse really should be loading those in the background while you are working.
Re:Splash screens == sloth by tintin on Monday February 20, 2012 @11:36AM (#3612868)
Of course Blender is lazy loading as you like to call it. Why load features the user is not using atm? The base of the program is just way better than lets say Photoshop.

Ever checked an online Photo editor? (http://pixlr.com/editor/ for example after a quick Google). Open the page and there it is: your interface ready to use.

Re:Splash screens == sloth by gt384u on Monday February 20, 2012 @12:08PM (#3612988)
To clarify, "lazy" isn't a pejorative in this case. It's just the technical term for deferring work until it needs to be done. "Eager" would be the term for doing everything right away.
Re:Splash screens == sloth by agravier on Monday February 20, 2012 @08:07PM (#3614696)
> I remember Blender loading fast as well. But are you sure every single feature of the program is available as soon as the GUI is displayed?

This is exactly the point made in the article...

Re:Splash screens == sloth by mikeash on Monday February 20, 2012 @12:13PM (#3613007)
Loading on demand is a vast improvement over loading everything up front, though. Loading on demand means you never pay the price for functionality that isn't used, and if your load time is divided into little pieces, it's far more likely to slip into spaces where the user is otherwise preoccupied, thus becoming essentially free. Lazy loading is a way to truly reduce loading time, not just a way to hide it as you seem to imply.
Re:Splash screens == sloth by talmand on Monday February 20, 2012 @02:09PM (#3613437)
Well, lazy loading is a way to hide loading time. But I didn't mean that lazy loading is bad since I think it is rather underutilized in desktop applications. Taking Photoshop as an example, I would explore the means to get the basic app up and running providing basic tools then load the rest in the background not waiting for demand. Loading on demand is nice as long as it can be done quickly. There's nothing worse than having the app loaded, click on a menu item, and then have to wait for that feature to load.
Re:Splash screens == sloth by orthecreedence on Monday February 20, 2012 @02:16PM (#3613465)
I think loading on demand is a vast improvement in some instances. For something like Photoshop, I'd gladly pay the initial 10 seconds for a more responsive interface. Photoshop is already slow, imagine dynamically loading resources on top of its usual sluggishness.
Re:Splash screens == sloth by bluedanieru on Monday February 20, 2012 @11:14AM (#3612795)
But are you sure every single feature of the program is available as soon as the GUI is displayed?

I hope not.

Re:Splash screens == sloth by pre on Monday February 20, 2012 @12:03PM (#3612969)
Blender's startup speed astounds me when compared to just about everything else I use. It starts faster than Vim half the time!
Re:Splash screens == sloth by mattmanser on Monday February 20, 2012 @10:33AM (#3612665)
Think of the 100s of millions or even billions of hours of unhappiness caused by whatever utter wanker designed the windows update system. All that misery waiting to go home to your actual life but you can't because your laptop's displaying 'Do not turn off or unplug your computer'. No, just sit here and watch me. Or those times you accidentally opened Word or Photoshop or MySql Workbench (god that's slow) or whatever. You made a mistake? Well fuck you. I'm not listening to you, says your computer, I'm just going to ignore you for a little bit.

That's why.

And they're not enormously complicated, paint opens instantly and has the same UI. Word is little more than a glorified textbox. Programmatically all the features make those programs enormously complex, but the actual common use of the programs are simplicity itself.

Re:Splash screens == sloth by georgemcbay on Monday February 20, 2012 @04:20PM (#3613984)
Have you used a recent copy of Word (eg. Word 2010) or any of the other Office software? It all opens basically instantaneously on my system, and my system is like 4 years old now. They still show the splash boxes this guy is complaining about but the splash boxes are blink-and-you-miss-it fast and then the real app is there. Less than a second from click to load of the real app.

The Adobe apps still do have more significant load times, more like 5-8ish seconds, but RAM is cheap, just load that app once and keep it open forever. Hibernate your system instead of shutting it down cold so that the apps don't have to reload from initial state when you next use them. This also makes Windows pop up very quickly (but even from cold boot modern Windows only takes like 15-ish seconds on my (again 4 year old) system), which isn't anything to complain about compared to any other desktop OS out there.

All in all, I'm in the group of people very confused about this post. I'm historically someone who absolutely hated long load times, but it isn't something I've worried about for any app or OS I use in years now.

Re:Splash screens == sloth by keypusher on Monday February 20, 2012 @07:33PM (#3614610)
You think they put that notification there to annoy you? No, it's because of possible data loss and/or system file corruption if you turn off the power while the system files are being patched. Splash screens exist because the program is loading. If you want the functionality of Paint, or Notepad, open those instead. If you want Photoshop, you open Photoshop, and it takes a while to load because it is gigantically complex. If you want it to load faster, buy a new computer.
Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @10:51PM (#3615152)
Surely Windows updates are applied via some sort of transactional system that can be rolled back and re-attempted if the process fails for whatever reason?

Having a power cut during a Windows update shouldn't result in a completely trashed system.

Re:Splash screens == sloth by pak on Tuesday February 21, 2012 @12:01AM (#3615277)
Surprisingly, NTFS does allow for transactions [1] and this feature is implemented since Vista, while as far as I know, HFS+ on Macs has no comparable feature. Therefore what you say may in fact be true.

I'm curious if cutting the power on a Mac while it's moving files into place will break a software update, or if the whole package receipt mechanism prevents that from occurring.

[1] http://en.wikipedia.org/wiki/Transactional_NTFS

Re:Splash screens == sloth by keypusher on Tuesday February 21, 2012 @01:05AM (#3615404)
I'm not sure even transactional NTFS would protect you in this case. From the wiki link:

Transactional NTFS is implemented on top of the Kernel Transaction Manager (KTM), which is a Windows kernel component.

Because this is implemented on top of the kernel itself, if you have brought down the kernel in order to update files within said kernel, you likely are not going to be able to leverage the transactional rollback. You might able to do a system restore, if you boot from CD, but breaking your kernel is not an easily recoverable situation. I suspect there are actually safegaurds in the update procedure which protect against this situation, but things can go wrong and it is really not something you want to have to rely on.

Re:Splash screens == sloth by jiggy2011 on Tuesday February 21, 2012 @02:24AM (#3615568)
I was thinking more of having a transactional system within the update software itself independent of anything on the filesystem.

Something like this:

1. Download all compressed archives that are required for the update from the update website and unzip somewhere.

2. Check the package manifest and figure out which files need to be changed/added/deleted.

3. Write a flag somewhere on the boot drive that says the update process has begun and which files will be altered.

4. Make copies of all the files which will be changed.

5. Work through the update process by modifying or overwriting the copied files with the contents of the update archives.

6. Temporarily suspend the scheduler so the update process is the only thing running and release locks on all of the files which will be changed.

7. Work through every file that needs to be changed and link the filesystem reference from the old version to the new version whilst keeping a copy of the old version.

8. At every stage in 7 mark in a log which references have been updated.

9. Mark a flag to indicate that the update process has been completed, either resume the scheduler and re-instate locks or force a restart of the OS if necessary.

When the system next starts up as part of the bootup process it can check if both the transaction start and finish flags are set. If the start flag is set but not the finish flag then it knows that an update failed so it can roll back by re-linking to the old versions of every file (reading the logs to know which files to re-link) and setting the start flag back to 0 so it can try again.

If the update was successful then it can delete the old files if the disk space is needed or keep them around in case there is an issue later which required a restore.

In regards the kernel example, my Linux install actually keeps old versions of the kernel on the system so that if a kernel update breaks something for whatever reason it is still possible to boot the system from the previous kernel. I imagine Windows and OSX do something like this , although possibly more transparently.

Note: This is what I could think of off the top of my head, I'm sure it's not a perfect way of doing it but it demonstrates the idea.

Re:Splash screens == sloth by Nick_C on Tuesday February 21, 2012 @04:28AM (#3615837)
I don't know if it follows those exact steps, but in the last few months I had several times a machine crash (flaky power supply) in the middle of various Windows Updates and it always recovered pretty well. It looked to this outsider like there was some sort of journalling going on.
Re:Splash screens == sloth by jmah on Tuesday February 21, 2012 @07:14PM (#3618603)
On HFS+ on OS X, most file writing is done atomically, by writing to a temp file and atomically switching the (conceptual) data pointer of the target file, aka FSExchangeObjects. It's common to end up with some of these temp files in ~/Library/Preferences, ending in .plist.asdfx, when the process was interrupted (so the original remains untouched).

This can be done for directories too - make a new one, write changed files and hard link unchanged ones, then FSExchangeObjects. Obviously this scales linearly with the number of files in the directory, so it's not perfect. I'm not sure if / how any of this is used for system updates, though.

Re:Splash screens == sloth by JBiserkov on Monday February 20, 2012 @12:27PM (#3613046)
> You made a mistake? Well fuck you. I'm not listening to you, says your computer, I'm just going to ignore you for a little bit.

The programs from Office 2010 have a _x on the splash screen which lets you easily minimize/kill the program in question. It's really snappy, works like a charm.

Re:Splash screens == sloth by talmand on Monday February 20, 2012 @10:44AM (#3612704)
Don't like that feature of Windows Update? Turn off automatic updates and do it manually when you wish.

Although I agree with the annoyance of accidentally opening something like Photoshop and having to wait to close it. But a good number of resources that is loading is third-party stuff that demands to be present immediately on startup as opposed to being loaded on demand. But whatever.

Paint has the same UI as what? I hope you're not comparing it to Photoshop or any other professional level software. I believe the modern version of Word is a good bit more than a glorified textbox.

But then you point out exactly why these programs load slowly in your last sentence. Maybe just start using less complex software?

Re:Splash screens == sloth by mattmanser on Monday February 20, 2012 @10:58AM (#3612743)
Their interface is the same. Are you utterly blind? Stop looking at the UX as a programmer and imagining the complexity of the features. The actual screen is displaying exactly the same stuff. There's a big white box to draw in and bunch of buttons to press.

You do not need to initalize all the 3rd party tools, you just have to find out which tiny little icon to add on a task bar or extra menu items to add, and why didn't you cache that when the extension was first detected?

And how silly of me, of course all the corporations these days let you turn off the updates on their computers don't they?

Stop telling your users that 'if they just..', do the opposite with UI than you do with your code, start programming for the best case scenario, not the worst case.

Re:Splash screens == sloth by talmand on Monday February 20, 2012 @02:03PM (#3613409)
The interface may be the same but I'm willing to bet under the hood they are quite different on a large scale. You seem unwilling to admit that.

I don't understand what you are saying about third party tools. Could you clarify? Is that whole sentence talking about the same thing because I read it as having four different topics in there.

If a corporation won't allow you to adjust update settings then that's an issue to take up with IT since they are preventing you from doing what you need, not the software itself. What if the default settings were exactly what you wanted and your IT department prevented it, is that also the fault of the software? I think your complaint is misdirected in this case.

Ask ten different people to define best case scenario and I bet you'll get several different answers. Which one do you choose? You can't make everyone happy but I guess since you're not happy then your way is the best choice? What you complain about telling users "if they just..." is what I call choice. When I say an application won't do something I need then I WANT the answer to be "if you just do this..." so I can have that choice.

Re:Splash screens == sloth by JS_startup on Monday February 20, 2012 @11:34AM (#3612858)
I once wrote a clone of Microsoft Word for a company looking to move away from Office dependency - I think you're really understating the complexity of something like Word when you call it a glorified textbox or say it should load as quickly as MSPaint because they both use the ribbon UI.
Re:Splash screens == sloth by irahul on Monday February 20, 2012 @03:11PM (#3613673)
>I once wrote a clone of Microsoft Word for a company

Out of curiosity, when was it? Wasn't openoffice.org an option?

Re:Splash screens == sloth by Hemospectrum on Wednesday February 22, 2012 @12:47PM (#3621732)
The chief complaint I have with HN's lack of reply notifications is that interesting questions like this one will go unanswered forever.
Re:Splash screens == sloth by freehunter on Monday February 20, 2012 @03:21PM (#3613722)
>Their interface is the same. Are you utterly blind? Stop looking at the UX as a programmer and imagining the complexity of the features. The actual screen is displaying exactly the same stuff.

Seriously? I mean, my Dodge Neon has the same gas, brake, clutch and steering wheel that a Ferrari 599 has, why doesn't it 0-60 as fast? Stop comparing engine size and complexity, it has all the superficial elements of a sports car! God, you're such a mechanic.

Re:Splash screens == sloth by Zarel on Monday February 20, 2012 @04:10PM (#3613949)
I think I understand what he's saying. Sure, your Dodge Neon may take longer to go 0-60 (i.e. it's okay if Photoshop is slower overall), but there would be something wrong with it if it takes significantly longer just to get in the car (i.e. Photoshop shouldn't take longer to boot up).
Re:Splash screens == sloth by freehunter on Monday February 20, 2012 @04:29PM (#3614014)
No, I think the engine metaphor is pretty apt. I completely understand what he's saying, but the alternative he seems to imply is no better. Why would I want the interface to load but not be able to use it for another 45 seconds? Okay, so I'm in my car (clicked on the shortcut) but I won't be able to go anywhere (use the application) for a few minutes because it's slow to accelerate (load). Who cares about the max speed of your car as long as it 0-60s in a reasonable amount time?

Either way it's going to take some time to load because it's a big application. One way lets you know it's working, the other makes you think it has frozen as you're fruitlessly clicking around. The interface is the least important thing in the application until it's fully loaded.

Re:Splash screens == sloth by Zarel on Monday February 20, 2012 @06:51PM (#3614471)
I think it makes sense. To extend your metaphor, you can do things such as turn on the radio without noticing a performance difference between the two cars.

The idea with Photoshop is, sure, loading the entire thing will take much longer, but users tend to use one tool at a time, and loading an individual tool shouldn't take anywhere near as long.

It also makes sense from the point of view of parallelization. One example of an extremely slow operation is waiting for the user to click on something. So instead of sequentially loading things, followed by the user deciding what to do, Photoshop should continue loading while the user decides e.g. what brush size and color he/she wants.

Like any other, this approach has advantages and disadvantages - it would indeed be frustrating if the brush tool hadn't loaded by the time you started using it, and it would probably require a lot of work for Photoshop to load so modularly and on-demand - but all I'm saying is, I understand the value in the alternative he suggests.

Re:Splash screens == sloth by freehunter on Monday February 20, 2012 @07:01PM (#3614497)
To go beyond cars and Photoshop, the RPG Guild Wars is a good example of only loading what you need. In fact, it doesn't even download the other game zones before you need them. If it sees you running towards the next zone, it begins a buffer in the background to pull in the data. So instead of making you wait while the game downloads and installs everything right up front, it downloads then loads up exactly what you need. This is much harder in an application, which is more non-linear.
Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @11:13PM (#3615197)
When you run a program the OS will usually just map the code into address space, it won't necessarily actually load the code from the disk until it needs to.

It's possible that what the program is doing at initialization is not loading code from the disk but doing something else, like perhaps checking it has a nice big contiguous area of disk to use for temporary storage or for loading some type of cache into.

There are many times in programming where you make a choice between taking a one-off up front cost to optimise something for faster overall performance vs slower overall performance without the setup cost.

For example with a DBMS you can lose some write performance by having an index on a table and rebalancing when you are writing but the advantage is much faster read performance.

Also A Java program can take longer to run the first time by JIT compiling the program for the platform it is run on but this will mean faster performance of the program itself.

Re:Splash screens == sloth by cageface on Tuesday February 21, 2012 @02:12AM (#3615542)
Personally I don't care how long it takes an app to start provided it stays running once it does start. If I'm doing non-trivial work in an app the boot time is negligible compared to the time I spend working in that app.

Given the tremendous engineering challenges apps of these size pose the last place I'd like to see developers spend their precious time is on this.

Re:Splash screens == sloth by darwinGod on Monday February 20, 2012 @11:00AM (#3612753)
Agree.I wouldn't care if MS Office,Photoshop takes some extra time to start.The wait would be worth it.For all the bashing Microsoft gets,MS Office and Active Directory are products which really,really way better when compared to their open source counterparts.So,let the engineers have their 30 seconds of glory! :-)
Re:Splash screens == sloth by viraptor on Monday February 20, 2012 @12:31PM (#3613067)
AD has pretty much no serious replacement, but MSO is for me as bad as everything else out there. Office in general constantly crashes and the only thing that is reasonable in Outlook is the calendar integration. It's so bad, that in 2007 it still didn't have a good threading view of messages. Communicator is a joke where you can't even do local list search - you either have to query global company address list, or manually scroll through your contacts...

In general no - I can't agree they're "really, really way better" than OS replacements. They're better for some people, worse for others.

Re:Splash screens == sloth by davedx on Tuesday February 21, 2012 @03:51AM (#3615767)
Loading times like that ARE UX. Wow. What do you think he's writing about? His Experience as a User.
Re:Splash screens == sloth by jarek-foksa on Monday February 20, 2012 @10:58PM (#3615162)
You don't write "enormously complicated programs" in the first place, you split big app into small pieces with as little coupling as possible to keep things simple.
Re:Splash screens == sloth by jiggy2011 on Monday February 20, 2012 @11:33PM (#3615220)
Personally I agree and usually prefer more "unix like" applications like this. However from a support point of view there is value in everyone running the same consistent program rather than several hundred mini programs piped together in some way.

It also makes purchasing easier, for example you can just buy photoshop/illustrator/whatever and have all the features you need straight up rather than having to choose between programs for different actions (say one program for drawing vectors , another for applying filter effects, another for format conversion etc etc).

Re:Splash screens == sloth by sixothree on Monday February 20, 2012 @03:48PM (#3613845)
What's wrong with letting the user browse for a file to open?
Re:Splash screens == sloth by jiggy2011 on Tuesday February 21, 2012 @05:34AM (#3615975)
you'll have to search the filesystem which means hitting the disk , moving the disk head away from where it was when it was loading the program.
Re:Splash screens == sloth by rsanchez1 on Monday February 20, 2012 @10:17AM (#3612609)
It's the same for any complex program, smartphone or desktop. I have Picsel Smart Office on my phone and it has a boot time, because it's an office app and has to load resources to use the app.

And on his proposed solution, he asks developers to empower users, to not make users feel belittled, and at the same time he asks developers to trick users into thinking the full app has loaded. How can you avoid belittling someone and trick them at the same time?