It doesn't matter if it's real or not. If something is perceived to be faster, for all intensive purposes to the end user it is faster. You can provide a stop watch, but the user won't care--they will go with the appearances.

Users have been conditioned to judge startup time by the number of times an icon bounces in the dock. Chrome is only perceived as fast because the feedback is different from the other applications. It's all relative. Once enough developers start using this trick that perception is ruined and developers will have to resort to splash screens and progress bars again.

But the point is that the app is already loaded. It's just shifting the burden of loading from dock click to startup. The users probably won't notice that their system takes longer to start because it already takes so long compared to the loading of one application. (At least for most systems. I try to keep it as short as possible.)

If lots of developers do this the negative effects will be longer desktop loading times, the time from login to usable desktop, and more idle memory usage. With memory so cheap, I wouldn't be surprised if this becomes more common, though personally I think it isn't polite to the user.

Actually, no. The program still starts up when you click on it except it doesn't register itself as a foreground application until after it is loaded. The time to start the application is exactly the same, bootup time is unaffected, but the icon just doesn't bounce.

If you want that effect, you could turn off the dock bounce for applications. The problem I have with Google's approach is that it seems like the application didn't launch until it gets into the dock. Like, I double clicked it, but maybe the second click was off? It seems like the computer hangs before launching it when it actually did launch it and just didn't get the icon in the dock.

If the number of bounces makes you think apps are slow to start, you can disable dock bouncing. But you're totally right that it does make it feel like Chrome starts up faster.

exactly. I see this non-bouncing in a dock full of bouncy icons as a pretty big differentiator and it wouldn't surprise me if the very light-weight apps begin using the code by default.