Anyways, it starts up in roughly 6 or 7 seconds on my spinning rust drive. I can't find this something to get worked up about, especially given the feature set of Adobe products.
Does the file you're opening use them? Why can't it load faster so if I've made a mistake opening the program I can close it before it does all that plugin loading?
Splash screens are just a lazy way of saying the user's time isn't valuable.
>Splash screens are just a lazy way of saying the user's time isn't valuable.
Wow. Hyperbole much? I'd rather get all my loading done up front instead of waiting per file or per action anyways. Secondly, it's 8 seconds or so per app start. Less if you have an SSD or a non-recommended-reqs system. Perspective.
Also consider these are pro-tier applications. The target market isn't going to be exiting their apps again and again, rather launch once and stay inside them.
I guess they could do some kind of lazy loading, but that'd be, you know, work to implement, and they're too busy with stuff like their own (broken) custom window routines to get Windowsesque MDI on the Mac.
If you see the new CS6 UIs (and the new tools like SpeedGrade), you'll see "plain and boring" grays, but the look is natural for the pro market. The splashes are completely antithetical to that look, and seeing a colorful Nickelodeon splash leading you to the somber grays in the UI is kind of bizarre.
People, in general, just have a hard time dealing with change.
I'm not a huge fan of the new icons/splash screens either, but I'm sure I'll get used to it and in a while CS5 will look dated.
That said, I'm a little more shocked that people are reacting more negatively to the splashes that are a bit more expressive. The past couple CS releases have been, from that perspective, plain and boring.