Re: IceWM-user Digest, Vol 49, Issue 1

Anthony Campbell <[email protected]> Fri, 18 Feb 2011 11:29:50 +0000
Newsgroups gmane.comp.window-managers.icewm.user
Message-ID <[email protected]>
On 17 Feb 2011, [email protected] wrote:
> Message: 8
> Date: Thu, 17 Feb 2011 11:37:34 -0800 (PST)
> From: Howard Arons <[email protected]>
> Subject: IceWM vs Fluxbox: Future of Ice
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8
> 
> I have happily used IceWM for quite a few years now. It seems to me that the prog is slowly going dormant.
> 
> Thus, from the icemw.org page: " "icewm ? 1997-2007 Marko Ma?ek (Apologies to the brave and the few who are still active develpoers/maintainers).
> 
> I have just started trying fluxbox, and its similarities to Ice are striking, at least to me. So, my questions:
> 
> 1. Is the development of Ice as dormant as it appears?
> 
> 2. Have others looked at fluxbox as a replacement? Liked it?
> 
> I don't want to start a flame war, I'm curious.
> 
> HaroldWho
> 
> 

Perhaps this just indicates that Icewm has reached perfection ...?  More
seriously, I have looked at Fluxbox, along with a lot of other WMs, and
can't see any way in which they are better. If Icewm didn't exist I
might use Fluxbox, but I can't see any reason to change to it. I
should just have to spend time learning how to configure it, only to end
up with a something more or less similar to what I already have in
Icewm. Why bother?

I'm actually in favour of minimalism in WMs. Eye candy, icons and the
rest I prefer to do without. In fact, I might even consider using
Ratpoison or similar, except that these seem to be too restricting in
certain ways.


-- 
Anthony Campbell - [email protected] 
Microsoft-free zone - Using Debian GNU/Linux 
http://www.acampbell.org.uk - sample my ebooks at
http://www.smashwords.com/profile/view/acampbell


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb