The Network Effect in action

he myths about “desktop Linux” are mostly associated and tied to “easy of use”. Many people, mostly ones with next to zero experience when it comes to GNU/Linux, have blindly decided that the slow growth of GNOME and KDE is due to an inherent problem other than marketing. But perceptions are changing when people discover that they are surrounded by GNU/Linux, even if their own client machine does not run a Free/libre operating system.

Whenever I perform scientific experiments, I entirely separate my work machine from the computational machines, which are dedicated to a particular task and are optimised for uptime, resilience, and good memory management. These machines exclusively run GNU/Linux, for technical reasons of course. In addition, soon enough one of the Windows clusters will be converted into dual-boot, permitting even more computational power to be amassed from remote nodes, provided one is not a Windows drone. In this modern age when just about any large cluster or computational server runs GNU/Linux, what can a Windows or Mac OS X user do to justify a choice of non-homogeneous platforms, wherein there is basically disharmony and inconsistency between the back end (server) and the desktop/workstation? There is a time penalty associated with moving a program from a proprietary desktop environment to GNU/Linux at the back room. It is not surprising that more and more people in my field are moving to UNIX or Linux on their desktop.

To what extent might the rise of Android impact people’s feelings towards GNU/Linux on the desktop? It does seem like iPhone has already managed to persuade some users to replace a Windows desktop with an OS X desktop. I see examples of this all the time, although as proof it’s merely anecdotal, not statistical.

It’s not e-waste until the hardware is dead

LOT of PCs that were perfectly fine 5 years ago were made obsolete not by dysfunctional hardware but by resource-greedy monopolistic and monolithic operating systems such as Windows Vista. This was bound to be a blessing to GNU/Linux, said one member of the Manchester LUG around 2006 when Vista was being finalised. He was right. Several years down the line, machines which were back then acceptable cannot possibly run the latest Windows, leaving GNU/Linux to fill the gap with its many distributions (suiting old and new).

Some machines, such as this one, come with Puppy Linux by default (I’ve just bought one to serve as a services monitor). There are other such machines that typically run GNU/Linux.

So yes, I’ve been checking about an extra unit to run a third monitor on. What strikes me as important is that the only two sites that I found so far [1, 2] both indicate that OpenOffice.org is a hot item even on Windows. With ODF and all, how would Microsoft feel? And to what extent will GNU/Linux benefit?

y most used and highly valuable applications are probably Kate, which I wrote about some days ago, and Thunderbird. KNode and Firefox used to be used a lot before I found ThunderBrowse.

Here is a sort of overview of how I used Thunderbird, in case someone ever thought of it as a weak application. Click on the image below for an explanation of my workflow in desktop 2.

everal years ago in this Web site I explained how I work with KDE. It was so long ago that it was KDE 3.1 and I also worked with 4 or 8 dual-head workspaces (now I have 10 that are actively used). But today I would like to share some working tips that are based on adaptations I made over the years in order to increase efficiency in workflow. The short story is, just as activities should be divided conceptually based on some criteria of commonality (e.g. which window needs to be near which other windows), so should text files. It sounds very obvious, but let’s have a better, more detailed explanation.

My favourite text editor is Kate (I use xbindkeys to launch a new instance of it with CTRL+ALT+W). It is very powerful for both development and for writing. It has syntax highlighting for loads of languages/markup, on-the-fly spellchecker, indentation, etc. It also can manage sessions, where basically one can save program state with settings and then load everything from a profile. This includes plugin settings, e.g. tabbed interface for text files. I started using this feature extensively years ago, especially with tabs. Some months ago, however, I found that sometimes I needed text to be in other desktops where it can be adjacent to the windows that correspond to it. For example, development I do in workspace 8, monitoring work in desktops 5 and 6, and news/research mostly in desktops 1 and 2. So I basically broke down my editor into 4 separate sessions, each of which containing particular text files of relevance. In the picture above, shown are two text editors in tandem. One has an archive of my past posts for quick lookup that requires little browsing/navigation, just text search in an enormous text file (tens of megabytes). The top part has about 4 files open, ranging from posts in progress, links that are accumulated, quotes I commonly use, and also some templates of value. There tends to be more in there.

The bottom line is, if you work a lot with text, consider working with raw text and a powerful editor. Putting the whole thing through an HTML-based piece of software like WordPress or even LaTeX-powered software/front ends like LyX is always possible to do at the end. But the real power is in words; the lighter and faster, the better. To improve access to files and information of interest, divide the text editors/sessions into separate desktops. This reduces movement between desktops and enables focus on particular activities, leaving distractions aside. If you have to open the file manager a lot, then perhaps a better workflow is being missed. Shortcuts too can help.

By the way, my KDE session as shown above has run for over two months without even a second login. The desktop’s robustness sure is impressive! The tips above apply not only to KDE. Other editors can achieve something similar.

My last KDE3 desktop on the left and the current KDE4 desktop on the right

Y FIRST experience with KDE4 was KDE 4.1. I had not had a reason to abandon what I was using back then (no upgrade treadmill). I finally started using KDE4 (full time) when 4.3 came out. From that point onwards I could not really go back to KDE3 and be happy. There was nothing in KDE3 that I really did not have in KDE4.

GNOME seems to be going through a similar phase of transition right now. Linux Mint is clinging onto GNOME2 and some users abandon GNOME altogether because of Unity or Shell. Eventually, however, it will probably stablise and users will come to accept change. It can take time (maybe years) and despite minor changes that take some time getting used to, KDE3 does everything substantial that KDE3 could do and it actually does a lot more with decent performance (comparable or better than) w.r.t. to KDE3 on the very same hardware.

All improvements come with a learning curve.

Summary: Weakness in 3-D desktop effects in KDE4

THERE seems to be a deficiency or a bug that may or may not be present upstream/in Compiz too (I seem to recall it not being present in Mandriva 2008 with KDE and Compiz). Basically, as the screenshots below show, the desktop wall separates the left and the right hand side monitors in a rather awkward way, such that they basically completely diverge and do not align horizontally, either (due to different screen sizes). For visual demonstration, here is what the wall looks like:

Here is what the sphere of my desktop looks like:

The connection between left and right is correct in this case. Scale and the other 3-D plug-ins work just fine, but the split in the wall is clearly a bug.

esterday I dumped visual media players — a decision that I stand up for at least for now — instead using more flexible scripts to play just particular parts of songs/tracks that I enjoy, even repeatedly. I use mplayer and bash to do the heavy lifting. This is handy when good segments, e.g. one part of a long concert, need to be isolated. Segments like these are usually to be found in very large files, which can be found either by name:

find -type f | grep PATTERN

To isolate large tracks (by file size), use something like:

find . -type f -size +{10000}k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'

$ find . -type f -size +50000k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }'

The self-explanatory shell script to write would look something like

mplayer /media/disk-8/Music/volO/AugMix.mp3  -ss 0:20:0 &
sleep 600
killall mplayer
mplayer /media/disk-8/Music/volJ/concert.ogg -ss 0:35:0 &
sleep 200
killall mplayer

Enjoy.