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

Openwashing Apple and Microsoft Proprietary Frameworks/Services

Viperr Linux Keeps Crunchbang Alive with a Fedora Flair

Do you remember Crunchbang Linux? Crunchbang (often referred to as #!) was a fan-favorite, Debian-based distribution that focused on using a bare minimum of resources. This was accomplished by discarding the standard desktop environment and using a modified version of the Openbox Window Manager. For some, Crunchbang was a lightweight Linux dream come true. It was lightning fast, easy to use, and hearkened back to the Linux of old. Read more

Openwashing Cars

  • Open source: sharing patents to speed up innovation
    Adjusting to climate change will require a lot of good ideas. The need to develop more sustainable forms of industry in the decades ahead demands vision and ingenuity. Elon Musk, chief executive of Tesla and SpaceX, believes he has found a way for companies to share their breakthroughs and speed up innovation. Fond of a bold gesture, the carmaker and space privateer announced back in 2014 that Tesla would make its patents on electric vehicle technology freely available, dropping the threat of lawsuits over its intellectual property (IP). Mr Musk argued the removal of pesky legal barriers would help “accelerate the advent of sustainable transport”. The stunning move has already had an impact. Toyota has followed Tesla by sharing more than 5,600 patents related to hydrogen fuel cell cars, making them available royalty free. Ford has also decided to allow competitors to use its own electric vehicle-related patents, provided they are willing to pay for licences. Could Telsa’s audacious strategy signal a more open approach to patents among leading innovators? And if more major companies should decide to adopt a carefree attitude to IP, what are the risks involved?
  • Autonomous car platform Apollo doesn't want you to reinvent the wheel
    Open source technologies are solving many of our most pressing problems, in part because the open source model of cooperation, collaboration, and almost endless iteration creates an environment where problems are more readily solved. As the adage goes, "given enough eyeballs, all bugs are shallow." However, self-driving vehicle technology is one rapidly growing area that hasn't been greatly influenced by open source. Most of today's autonomous vehicles, including those from Volkswagen, BMW, Volvo, Uber, and Google, ride on proprietary technology, as companies seek to be the first to deliver a successful solution. That changed recently with the launch of Baidu's Apollo.

today's leftovers

  • KDE Applications 18.04 Brings Dolphin Improvements, JuK Wayland Support
    The KDE community has announced the release today of KDE Applications 18.04 as the first major update to the open-source KDE application set for 2018.
  • Plasma Startup
    Startup is one of the rougher aspects of the Plasma experience and therefore something we’ve put some time into fixing [...] The most important part of any speed work is correctly analysing it. systemd-bootchart is nearly perfect for this job, but it’s filled with a lot of system noise.
  • Announcing Virtlyst – a web interface to manage virtual machines
    Virtlyst is a web tool that allows you to manage virtual machines. In essence it’s a clone of webvirtmgr, but using Cutelyst as the backend, the reasoning behind this was that my father in law needs a server for his ASP app on a Win2k server, the server has only 4 GiB of RAM and after a week running webvirtmgr it was eating 300 MiB close to 10% of all available RAM. To get a VNC or SPICE tunnel it spawns websockify which on each new instance around 20 MiB of RAM get’s used. I found this unacceptable, a tool that is only going to be used once in a while, like if the win2k freezes or goes BSOD, CPU usage while higher didn’t play a role on this.
  • OPNFV: driving the network towards open source "Tip to Top"
    Heather provides an update on the current status of OPNFV. How is its work continuing and how is it pursuing the overall mission? Heather says much of its work is really ‘devops’ and it's working on a continuous integration basis with the other open source bodies. That work continues as more bodies join forces with the Linux Foundation. Most recently OPNFV has signed a partnership agreement with the open compute project. Heather says the overall OPNFV objective is to work towards open source ‘Tip to top’ and all built by the community in ‘open source’. “When we started, OPNFV was very VM oriented (virtual machine), but now the open source movement is looking more to cloud native and containerisation as the way forward,” she says. The body has also launched a C-RAN project to ensure that NFV will be ready to underpin 5G networks as they emerge.
  • Ubuntu Podcast from the UK LoCo: S11E07 – Seven Years in Tibet - Ubuntu Podcast
  • Failure to automate: 3 ways it costs you
    When I ask IT leaders what they see as the biggest benefit to automation, “savings” is often the first word out of their mouths. They’re under pressure to make their departments run as efficiently as possible and see automation as a way to help them do so. Cost savings are certainly a benefit of automation, but I’d argue that IT leaders who pursue automation for cost-savings alone are missing the bigger picture of how it can help their businesses. The true value of automation doesn’t lie in bringing down expenses, but rather in enabling IT teams to scale their businesses.
  • Docker Enterprise Edition 2.0 Launches With Secured Kubernetes
    After months of development effort, Kubernetes is now fully supported in the stable release of the Docker Enterprise Edition. Docker Inc. officially announced Docker EE 2.0 on April 17, adding features that have been in development in the Docker Community Edition (CE) as well as enhanced enterprise grade capabilities. Docker first announced its intention to support Kubernetes in October 2017. With Docker EE 2.0, Docker is providing a secured configuration of Kubernetes for container orchestration. "Docker EE 2.0 brings the promise of choice," Docker Chief Operating Officer Scott Johnston told eWEEK. "We have been investing heavily in security in the last few years, and you'll see that in our Kubernetes integration as well."