Some apps, like my browser, mail program, the terminal, Emacs, ... I love having start quickly, even if it's because they were just in the background before.
Other stuff, like Preview, I don't use often enough to care about the load time, and I would probably configure it to exit when the last window closed.
Under Lion, that is (sort of) what Preview and TextExit do. When you close all open documents in Preview and then switch away from the app, the app will terminate.
That's the whole paradigm. Windows belong to applications, but applications aren't windows. That's one reason the menu bar is divorced from any window (along with Fitt's law): so that you can interact with an app even when it currently has no windows open.
I do not understand what you are saying. Can you elaborate?
Edit: As to my original comment, when I switch to another app, preview stays open, but up to now I don't know how to close it because I can't get the menu to appear without a pdf or something using it, that's why I reopen a document, forcing the menu to show up, then close the app.
As far as the menu disappearing when you close both documents, that's confusing and directly contradicts what you typed earlier. I can open Preview.app, and it'll just show me the menu. I can close it by alt-tabbing to it and hitting Cmd-Q - no windows required.
Basically with command held down the entire time, hit tab until Preview is framed, and instead of releasing command (which would pull Preview to the foreground), hit Q, which will send Preview the command-q event and cause it to quit.
You could just close it from the dock you know. Or switch to it and command-Q immediately.
In fact, I don't even understand how you'd go around to "reopening a window" of preview, preview will not open any window without a document in it, do you open a document just to close preview or something?
I think the point the author is trying to make is that it shouldn't be up to the consumer to spend more money to make their programs run faster. Software reform is what's needed and "just buy an ssd" is a very strong argument.
Having said that, I agree with the idea of making software less monolithic and making it start up as fast as possible, as long as it is possible. However, when I say that I want a program to start up fast, I mean that I want it to start being useful fast. Quite a few of author's ideas are not about bootstrapping gradually, they're about faking it. It's like going to a place that used to have a "closed for lunch" sign and discovering that it's now open, but populated by robots whose personality is an Eliza-like AI.
And I agreed about the "faking" issue. Just like how Windows will silently keep loading tons of services in the background after a reboot, but shows you a desktop and makes you think you are free to click and launch stuff.
But quite a few of those ideas are useful.
The only ones I thought were a bit out-there were the ones about "just processing it in the cloud" while the local copy is still loading. But other HNers are probably more qualified to judge how realistic this is.
What is a possibility, however, during loading a lot of time is spent on loading all sorts of modules, ones that might not even be used that session, and most definitely not in the first few minutes. Because what is the user going to do first? Most likely it'll be `File > Open ...` and browsing through the filesystem looking for whatever project they intend to open.
You don't need any plugins for that. And it's exactly the type of task that spends relatively a lot of time waiting for user input and not so much time computing or loading things. During this task the app can continue loading modules and plugins and the user doesn't have to wait because they're selecting a file.
You probably need to disable (most of) the instant preview in the file open dialog until it's done loading, but that's a minor trade-off.
Of course you're loading the modules necessary for opening files first (most recently used filetypes first). When that's done the dialog can start showing previews. If the user happens to have found and selected their file before it's done, then, only then they'll have to wait.
Now you're loading the file and it's showing on the screen, the user can browse the layers a bit and ponder where exactly they left off last time. A wonderful time to load the rest of the modules! Of course the features used in this project will be loaded first. If there's no text layers, we can put off loading font-rendering support in favour of other modules.
It's not all load-on-demand, but a lot of user tasks are not as processor- or data-intensive as you'd think, because the user is busy thinking and as long as the UI is responsive enough they're happy.
However with (let's say) eclipse or photoshop , when the program loads the first thing it displays is either my code or a graphic I am working on.
How would it allow me to interact with that in any kind of useful way without actually loading the program?
I created a web app recently that had to make an Ajax call but could not allow any user input until this action had completed as various parts of the UI would have to be refreshed with new information.
I had reports from users that they thought the app had crashed since it wasn't responding to their inputs for a few seconds. It turned out the best solution was to simply whiteout the entire page and show an animated egg timer until the action had completed.
It's only really heavy professional apps that take much time to start anyway.
Facebook, Linkedin, Flickr, IMDB, Dropbox, Angry Birds, Skype, iGo, Quotes, PCalc Lite...
Display a launch image that closely resembles the first screen
of the application. This practice decreases the
perceived launch time of your application.
Avoid displaying an About window or a splash screen.
In general, try to avoid providing any type of
startup experience that prevents people from using
your application immediately.The idea is to give the user the impression the app has already started instantaneously, and you're just waiting for data to roll in to populate the UI.
The app needs to load something close to 200 fonts (it's a design-oriented app). If they're not all present, the font choice list won't render properly. Lazy-loading isn't really an option -- otherwise the user will be sitting there watching the UI slooowwwlly render each font choice, one by one, while he waits to do something with them. Better to take the hit at startup, IMO, rather than making the user pause while he's in the middle of creating something.
No, it's just vastly more complicated than most of the cut-down alternatives because it has to meet the needs of pro designers. Maybe there's some accumulated cruft there but I can guarantee you that Pixelmator, for example, would be similarly large if it had to support all the same use cases.
Many people install pirate Photoshop to resize and put a few filters on their photos and complain that is it too slow and complicated when really they could have achieved the same result from either a freeware program or a significantly cheaper commercial one.
You can kind of achieve this with Windows + Adobe stuff too. Just don't quit Photoshop when you're done using it, and don't turn the computer off, put it to sleep. If you have an SSD (like your iPhone), then swapping Photoshop back into main memory will also be much faster.
Of course the OP is right, Adobe stuff is bloatware and sucks. Fortunately for non-pro designers, there are alternatives like Pixelmator and Paint.NET.