Language Selection

English French German Italian Portuguese Spanish

A Month With Fluxbox - Part 2

Filed under
Reviews

My month with Fluxbox can almost be officially over and it's time to report on my experiences as promised. I wish I had a long list of complaints to file or problems for which I had to find answers or even less than compelling reasons to run back to KDE (i.e. something interesting or controversial to write about). But the truth is, it sat back there serving up my windows and never once gave me reason to even notice it was there. And that's a good thing.

I sat it up in the beginning about the way I wanted it and tweaked it some a week or so later, and have since just been running my applications and doing my thing without any problems. I don't know what I thought I'd have to write about a month later, but what can I say? It managed my windows, displayed a pretty wallpaper and let me layer idesk, fbpager or torsmo ontop. It did what it was supposed to do! It did it efficiently, stably and quickly. I didn't experience the first crash of any sort. Everything was always fast and responsive. It's just been an uneventful month.

I continued to run my kde applications because I like them mainly, have all my mail saved in kde maildirs as well as all my bookmarks are in a konqueror xml file and I like the font rendering in kde applications. So perhaps I had the best of both worlds here this month - my favorite applications sitting on a fast stable window manager.

I guess the question is, do I go back KDE or just stay in Fluxbox? I've pondered this last few days with the added option of trying a different window manager for May. But back to the original question, which is leading up to a comparison of sorts... Now to the outside world this would seem an unfair competition as kde is a full-featured desktop environment. But what you probably don't know about me is that I don't use a lot of those fancy dancy features and extras kde includes. I use the window manager portion to run kontact and konqueror mostly. I like my mplayer that requires X - any X implementation will do, as is the same deal with my games such as Doom3, gimp, and an occasional instant messenger. In addition, I like a monitoring application whether it be gkrellm or torsmo. So point being - Fluxbox does all this as well, and just as well as KDE. I do everything else from the commandline. I don't even use desktop icons in kde, I usually delete them. I just set up idesk for something to show Fluxbox capabilities and "purty up" my screenshots. So, I guess all this to say, I used Fluxbox for a month after using KDE for 5 years, and well, I mean no offense, but I just plain didn't know the difference.

As far as performance, again that would almost seem on the surface as an unfair comparison considering the size and features of each. But as stated I don't use a lot of kde background and extra features, and since kde has performed it's latest voodoo on 3.4 I'm afraid the only performance difference I could detect was when I first log in and start a kde application under Fluxbox. Those applications did take a few seconds longer to load than they do in KDE the first time - but that's because of having to set up the dcop stuff and load the libraries that would be ready to go under KDE. I suppose this equals out as Flux only takes about 3 or 4 seconds to go from start command to ready desktop and KDE takes about 30. After that first start, they open as fast and function as well as they do in KDE. So, again, I just didn't notice any difference.

Setting up the wallpaper was a little more trouble in Fluxbox because I have to load kuickshow or something to look around in my wallpaper archive to pick one out first, then edit my init file. Too many times a wallpaper looks good on a site or even as you look at it during a kuickshow slideshow, but it doesn't look as great on the desktop as a wallpaper. So, having to change wallpapers a few times could almost be a drag except that Fluxbox has a restart in their menu. One might expect a window manager to crash after doing this a half dozen times or so, but Flux never did.

So, at the end of the month I have to report that I have nothing to report. There was no clear cut winner or loser here. I love them both. I believe my experience is very personalized and do not dare to say to anyone else they'd notice little or no differences to speak of as well. It's because I'm a commandline junkie that this happened to work out this way for me. I feel like I'm short changing all parties concerned here: KDE, Fluxbox, and my readers. I do feel some attachment to Fluxbox as it started out just a practically empty window and I had to set it all up from scratch. It can almost be described as that same ownership and freedom kinda feeling one gets from running Gentoo or LFS.

So am I going back to KDE?

Eventually I bet I will, especially when a lot of 4.0 stuff starts showing up in cvs. But for now... I think I'm gonna try enlightenment. I've seen some really cool features in screenshots and when I ask about them, I've been told its an enlightenment thing. So, perhaps I'll do a month with enlightenment next. ...if I can tear myself away from Fluxbox. Smile

More in Tux Machines

Leftovers: OSS

OSS in the Back End

  • Open Source NFV Part Four: Open Source MANO
    Defined in ETSI ISG NFV architecture, MANO (Management and Network Orchestration) is a layer — a combination of multiple functional entities — that manages and orchestrates the cloud infrastructure, resources and services. It is comprised of, mainly, three different entities — NFV Orchestrator, VNF Manager and Virtual Infrastructure Manager (VIM). The figure below highlights the MANO part of the ETSI NFV architecture.
  • After the hype: Where containers make sense for IT organizations
    Container software and its related technologies are on fire, winning the hearts and minds of thousands of developers and catching the attention of hundreds of enterprises, as evidenced by the huge number of attendees at this week’s DockerCon 2016 event. The big tech companies are going all in. Google, IBM, Microsoft and many others were out in full force at DockerCon, scrambling to demonstrate how they’re investing in and supporting containers. Recent surveys indicate that container adoption is surging, with legions of users reporting they’re ready to take the next step and move from testing to production. Such is the popularity of containers that SiliconANGLE founder and theCUBE host John Furrier was prompted to proclaim that, thanks to containers, “DevOps is now mainstream.” That will change the game for those who invest in containers while causing “a world of hurt” for those who have yet to adapt, Furrier said.
  • Is Apstra SDN? Same idea, different angle
    The company’s product, called Apstra Operating System (AOS), takes policies based on the enterprise’s intent and automatically translates them into settings on network devices from multiple vendors. When the IT department wants to add a new component to the data center, AOS is designed to figure out what needed changes would flow from that addition and carry them out. The distributed OS is vendor-agnostic. It will work with devices from Cisco Systems, Hewlett Packard Enterprise, Juniper Networks, Cumulus Networks, the Open Compute Project and others.
  • MapR Launches New Partner Program for Open Source Data Analytics
    Converged data vendor MapR has launched a new global partner program for resellers and distributors to leverage the company's integrated data storage, processing and analytics platform.
  • A Seamless Monitoring System for Apache Mesos Clusters
  • All Marathons Need a Runner. Introducing Pheidippides
    Activision Publishing, a computer games publisher, uses a Mesos-based platform to manage vast quantities of data collected from players to automate much of the gameplay behavior. To address a critical configuration management problem, James Humphrey and John Dennison built a rather elegant solution that puts all configurations in a single place, and named it Pheidippides.
  • New Tools and Techniques for Managing and Monitoring Mesos
    The platform includes a large number of tools including Logstash, Elasticsearch, InfluxDB, and Kibana.
  • BlueData Can Run Hadoop on AWS, Leave Data on Premises
    We've been watching the Big Data space pick up momentum this year, and Big Data as a Service is one of the most interesting new branches of this trend to follow. In a new development in this space, BlueData, provider of a leading Big-Data-as-a-Service software platform, has announced that the enterprise edition of its BlueData EPIC software will run on Amazon Web Services (AWS) and other public clouds. Essentially, users can now run their cloud and computing applications and services in an Amazon Web Services (AWS) instance while keeping data on-premises, which is required for some companies in the European Union.

today's howtos

Industrial SBC builds on Raspberry Pi Compute Module

On Kickstarter, a “MyPi” industrial SBC using the RPi Compute Module offers a mini-PCIe slot, serial port, wide-range power, and modular expansion. You might wonder why in 2016 someone would introduce a sandwich-style single board computer built around the aging, ARM11 based COM version of the original Raspberry Pi, the Raspberry Pi Compute Module. First off, there are still plenty of industrial applications that don’t need much CPU horsepower, and second, the Compute Module is still the only COM based on Raspberry Pi hardware, although the cheaper, somewhat COM-like Raspberry Pi Zero, which has the same 700MHz processor, comes close. Read more