Tidying up after Linux 16780

snips

Larry Qualig

Frequently. The usual is three desktops and a spare:

One for development One for internet One for documentation Often the spare will be used for administration

A typical scenario is writing, testing and docuementing web-based code. The actual development tools are in one desktop, the documentation tools - even just for keeping notes on what's done, need doing, etc - are in another, a browser and the likes are open on another, for testing, and on the fourth, administration tools for the web server, an editor window or two for the documents being tested against, that sort of thing.

It's not so much being able to switch between coding and dungeon crawling, but rather, compartmentalizing sections of a larger task that I find important.

Once you're used to working that way, though, not being able to gets really annoying. You also get the habit of using the desktops - set the system up to load up all your tools, each in its proper desktop, automagically; if you're not doing a coding session, your net tools are still up, if you're not doing a net session, your documentation tools are still up, etc. Sitting in the background, on another desktop, they're not in the way, so just leave 'em running.

This is one reason the incessant "OOo opens so slowly" thing is so silly, IMO. OOo, here, opens in something like 1-10th of a second - because it's sitting there, on one of the other desktops, ready to use in the time it takes me to switch desktops. Whether it takes 3 seconds or 3 minutes to load initially, who cares? It's ready, instantly, when I need it, so where's the problem?