Monday, 4 October 2010

Hybrid - a horror or not?

It was remarked recently that I'm a bad Linuxer because I use a hybrid desktop - hybrid in this case meaning a mix of GTK (AKA Gnome/XFCE), QT (KDE3.5 and 4.x) and Windows (via Wine) applications.
To this I say: What's wrong with that?

Now, I understand that if you keep all things native to your current session, eg Gnome apps in a Gnome session, KDE ones in a KDE one and so on, then you'll likely have better overall performance and a uniform look.
But the downside of this is that some of the session specific options I don't like, and want what I want instead.
Even though this means having my GTK apps look different to my QT ones, I don't mind that. I could use the QT or Oxygen engines for GTK, I could use the GTK engine for QT, but I don't want to.

What this boils down to is that I like things my way, and I couldn't care less what widget set or session it was made for - if it runs with the ones I'm using, then I'll use it.

This is especially useful right now, since I've changed my desktop again. To what? Well, not Gnome, as I've fallen out with it again.
No, this time it's KDE, but not the monster of the KDE4.x series - Thanks to the Chakra project, based on Arch Linux - which conveniently, I use - I've dug out the kdemod-legacy repository, giving me the older KDE 3.5 desktop - and it beats even the 4.x series. Yes it's unsupported. Yes, 4.x has all those flashy bells and things. Yes, I still use some Gnome apps. But overall, KDE 3.5 is one of the better sessions I've had.

It's customized, naturally. The default panel was shrunk down to the K Menu and a CPU monitor, and is auto-hidden in a corner, appearing only when I need it. Everything else is taken over by the Avant Window Navigator at the bottom.
Compiz and Emerald replace Kwin as the window manager of choice. While this takes up a little extra resources, it provides a few things Kwin can't.
And that's actually where KDE stops, because most of the applications I use are actually GTK-based.
OpenOffice, while not strictly speaking a GTK app, pulls it's theming from the current GTK settings. Since KDE has a handy module for choosing the GTK theming while in a KDE session, this isn't a problem, even if I use a KDE colour scheme that normally upsets OpenOffice - which is often.
Pidgin has taken over from Emesene (MSN) and XChat (IRC), also taking support for Google Chat and Twitter, bundling them all neatly together into one GTK application. Pidgin's plugin framework makes it unparralelled for those who use lots of IM networks, let alone those who use IRC and more on it.
Transmission Bittorrent... well, actually I'm trialling the QT interface for it, which I previously hadn't known about. So far so good, except for one mysterious crash I can't seem to replicate, but if I find any real problems, it's back to the good old GTK one.
Lastly, Firefox.

Regulars will know that Iron and Firefox regularly clash over my favour. However, through now fault of it's own, Iron has finally lost out for good.
The main reason is XMarks. If you don't know what it is (or possibly was) it's a cross-browser and platform bookmark sync tool. It's kept my Firefox and Iron bookmarks up to date and synchronized so that no matter which one I added a bookmark in, both had it.
However, they're discontinuing their service, and there doesn't seem to be any alternative that works for both Chrome and Mozilla based browsers.
So once more, I've tweaked out Firefox with a ton of extensions, with Firefox Sync supplanting Xmarks.

One further note on Firefox though, specifically the TACO extension.
There's a little controversy going on over TACO since TACO 3.0.
TACO 2.0 (Which lives on as Beef TACO) was an invaluable tool for blocking and opting-out of a lot of unwanted things. I'll let you read up in more detail on the Beef TACO page here: https://addons.mozilla.org/en-US/firefox/addon/180650/
TACO 3.0 'with Abine' sees a massive increase in the size of the extension, and adds this Abine thing. This appears to be some kind of iTunes store like extra where you can purchase extra functionality, at the cost of some massive reduction in performance, with it nagging you pretty much constantly.
The same results TACO 3.0 offers, without this and without the massive footprint, can be achievevd through several smaller extensions. Beef TACO, of course, replaces this. Add in the BetterPrivacy and NoScript extensions, and you're set to go. Adblock is an optional extra. Alternatively, if you don't like the way NoScript handles it, set up Adblock and Flashblock instead. Flashblock conveniently handles Silverlight as well, making it more useful.
Stop Autoplay is another optional addition, removing yet another web annoyance.
OptimizeGoogle is useful for removing a lot of junk from Google's search and other tools.
Greasemonkey, and by extension Greasefire, is also useful. Pull in user scripts that work on pages and you can enhance things yet further - not to mention some scripts are also capable of handling some parts of what TACO 3.0 tries to do.

Basically, there are better ways to handle it than TACO 3.0 - and all of them, regardless of what these Abine people think, are better than TACO 3.0

In similar Firefox news, since I tweaked it out, I found some interesting new extensions. I won't go on about them here, instead I'll just list them. You can look them up yourselves.
If there's interest though, I might turn it into a collection if people want to see just what I use and why.
So here's the official YACB interesting new extensions list:
All-in-One Sidebar
App Tabs
Hide Caption Titlebar Plus
Liquid Tabs
RightToClock
Tab Progress Bar
Tab Wheel Scroll
Unread Gmail Favicon

That's all for now.
Until next time, keep rocking.

No comments:

Post a Comment