FluxBlog
I have rather a penchant for doing goofy things. Like running a full GNOME install on a laptop with 256 megs of RAM. One day, in a fit of lunatic excess brought on by a combination of constant disk-thrashing and recent blogging about lightweight desktop options, I ordered some RAM from NewEgg, and moved to Fluxbox in the interim. The shocking thing is, now that the RAM is installed, and my hard drive has ceased doing an imitation of a manic organ grinder, I cannot for the life of me find a good reason to switch back to GNOME.
Now, this is uncanny considering that I’ve always used GNOME, and find it a pleasant and esthetically pleasing environment, not to mention the fact that I tend to develop withdrawal symptoms whenever I force myself to try something else. So why, then, do I find within myself a curious indifference to the idea of switching back to GNOME?
Probably the best way to start out is to explain what I find so spiffy about Flux, as it is affectionately abbreviated by it’s partisans.
To start with, all Flux’s configuration files lie within the ~/.fluxbox directory. They are quite well-formed, singularly uncluttered text files, in the grand old Unix tradition. I find them a pleasure to edit. This must be compared rather favorably to GNOME’s GConf, which, while better than a certain abomination from Redmond, cannot hold a candle to the simple beauty of the flat text file. Keybindings? Text. Menu files? Text. Init files? Text. And it’s not just that the files are a joy to work with, they also allow you to modify virtually every aspect of Flux. I cannot tell you how many times I thought “It would be nice if this were possible”, and finding upon perusal of Flux’s concise yet comprehensive man page that it was indeed easily done.
Fluxbox also looks quite pleasingly clean and simple. That is, when you notice it. Actually, there’s usually not much of it on screen. That’s a good thing, as a certain female head of a a major commercial conglomerate is wont to say. Flux is remarkably themeable, allowing the use of color gradients and blending, or pixmaps, all yet again defined in a simple text file. Googling for screenshots will pleasantly surprise you, I am sure.
At first I thought that I would miss GNOME’s menu bar. Then I realized that I never used it for launching applications anyway, preferring instead to use launchers and the run dialog. I do somewhat miss the auto-addition of apps to the menu via desktop files, but if you keep track of what’s going on, you can add them to the menu file yourself. There are several “generate menu” script for Fluxbox, but all that I tried missed a good chunk of apps. But, as I say, if a good run dialog and launchers are available, I don’t use the menu anyway.
Fluxbox includes a taskbar with a window list, a notification area, a desktop switcher, a clock, in short most of the useful necessities. Not to mention a delightful feature known as window tabs. Think Firefox, people. And if you don’t need these things, or want them somewhere else, the only thing standing between you and your desires is a text editor.
Oh, and of course, Fluxbox’s demands on your system’s resources is next to negligible. Plus, it’s remarkably stable and is backed by a pretty vibrant community. Now there are a handful of other apps that make up my new desktop, and I may talk about them later, but Fluxbox is at the core. The fundamental attractiveness of Fluxbox is that it just works like I want it to. I almost forget it’s there sometimes, it works so seamlessly.
6 comments April 8, 2008