The case for lazy loading

For music recording I’ve started using Pro Tools as my first-class choice. I struggle with this, because I find it to be a far, FAR inferior product to products like Cakewalk Sonar, for example. But I’m using it because it does offer specific features for the hardware I’m using.

Anyhow, Pro Tools has a splash screen and it takes around 3 to 5 minutes to load the application. Most of this time is looking for and loading “plug-ins”.


Why is this frustrating? Why am I writing a blog post, in the time it takes to load this application? Because I don’t use ANY of these plug-ins, currently. So, I have to pay the price, for something that I don’t even use – every time I start the application.

The lesson here, I think, is that as developers, we need to be aware that our Users’ time is valuable. We shouldn’t waste it, making them wait, for something that isn’t critical for the application. And Pro Tools, every heard of loading things in the background?

As an alternative, I would think the software would want to enumerate the plug-in’s, but not actually load them until they are needed or requested. This splash screen drives me nuts every time I see – what a poor interface design decision this was, in my opinion.

Posted in Best-practices, Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Enter your email address to follow this blog and receive notifications of new posts by email.

Join 9 other followers

%d bloggers like this: