aseigo.blogspot.com/2005/03/everybody-get-together.html
a few months ago i noted how insanely great konsole was when it came to m emory consumption, especially compared to launching a bunch of xterms. p erhaps one would have thought that this good news would've been greeted with enthusiasm. or at least that people would go out and try and verify those results and be happy when they found out for themselves how effic ient tabbing in konsole tends to be. instead, the reaction i received was like a bucket of cold water in my fa ce. many people, including some of our own core devels, decided to inste ad naval gaze about methodologies and poo-poo the idea that our software really was that great. granted, my observations were the digital equiva lent of "back of the envelope" calculations, but they were generally acc urate. ever wonder why people don't talk about KDE's efficiency? today i read in Ben Maurer's blog that Konsole takes "takes 50 kb per tab ". he notes that even after Aivars Kalvans's great work on gnome-termina l, konsole is still 5 times more efficient with memory per new tab. now, how do you think he will be received by his community by announcing gno me-terminal's improvements? will those same people who decided to get into a pedandist's duel when i said that konsole was so much better than xterm due to it's per-tab effi ciency head off to correct Ben? Come on you people now Smile on your brother Everybody get together Try to love one another right now it don't hurt to let someone else smile once in a while... so here's today's cool note about something KDE's doing right IMHO: KIMPR oxy. the KDE instant messaging proxy provides an interface that any IM a pp can implement to publish information about who is online at the momen t in turn any other app can subscribe to this information and use it as it makes sense. so, for instance, kmail can show you that the person wh o sent you the email you are currently reading is online. whether that p erson is online in kopete, or kontact or any other such app. instead of hardcoding interoperability between applications, which is sho rt term thinking and brittle, KDE has built generic facilities for worki ng together so that we may build applications out of smaller pieces of e xisting technology. in fact, this allows us to build new applications, e ven new types of applications, tomorrow without having to reinvent all t he interoperability we've put in place everywhere else. this makes so mu ch more sense than anything else out there and is really starting to sho w in our applications.
I see that the memory, and resource, usage of Gnome as a who le has hit the proverbial fan. I know, I used Gnome and especially Evolution quite a bit for eigtheen months circa 2001, 2002. That was before they really decided to put what they perceived to be Enterprise Features(tm) in it as well. down in front of several people who haven't used it (or KDE, or Unix-like systems) before, got them to use it for a while and found out the reality. Anyway, what I will say is that getting an efficient desktop and applications is a heck of a lot more than running valgrind or a memory profiler. It's the base toolkit and programming tools that you use, the level of re-use that occurs and all of those little things throughout that all snowball and combine to make an efficient desktop environment. Microsoft have had resources to panel-beat Windows into shape, but Gnome and KDE don't have that. I can only imagine how that complexity will increase with additions in the future like Cairo etc.
|
http://csua.com/feed/