The contents of decks persist between invocations of DeckScape. The key benefit of the deck abstraction is that it provides a way to organize material. DeckScape is also multi-threaded. In particular, fetching a new page occurs in the background, in a separate thread. Thus, unlike single-threaded browsers, traversing a slow link or downloading a large file does not freeze the entire application.
All decks remain active and ready for browsing, and multiple links can be traversed concurrently.
This would have the advantage that, when traversing a slow link or downloading a large file, the other instances would remain active. However, multiple instances have the drawback of increasing the amount of computer resources consumed. When DeckScape is first run, the user sees a window containing a menu bar and a large open area. This window forms the workspace in which the user positions decks and pages. Clicking links adds more pages to the deck.