I don't use any window manager, if I want a GUI I use Windows. I use Linux/BSD heavily for servers though and gnu screen is about as close as I get to a window manager there, so no comment on that part.
For wireless, I have also given up on Linux a couple of years ago. It's just far too unreliable. The best I could do was to set it up to statically always connect to the same wireless network, which was fine until that network was unavailable (e.g. I actually took the laptop anywhere) in which case it would add a few minutes to the boot time waiting for it to connect. nm-applet and wicd are just as crap as each other and there doesn't seem to be a good solution to this. Tiny patches tend to completely break them too.
On top of that, linux absolutely sucks for battery life. A 7 hour laptop in Windows became a 2 hour laptop in Linux, with hibernate/suspend not working properly (quirks) either.
This was Linux on 3 laptops over a period of about 5 years, so it's not just down to one incompatible laptop.
Combined, I concluded that Linux was just not good enough for Laptops on their two most important features, so I use Windows for Laptops and Desktops and have a rack of Linux/BSD machines in my attic doing an amazing job of serving them all behind the scenes.
Originally Posted by transhour
if gnome 3 is the least bit unstable it would take the debian team the next 8 years to get around to it...
even at release time, debian is already about 6 months out of date, but that is part of their ideology, a lot of work goes into it, i think i once read it takes an average of 2 years for a package to enter sid, to make it to stable...
I will say that Debian has been getting a lot better at this recently. The only packages I see that are still significantly out of date seem to be from the 3rd party debian-multimedia repository. 3-6 months behind to wait for stability seems reasonable to me but they used to be a year or two behind. If you don't like it, you can just switch from the "stable" release to "testing" to get quite up to date without going into the dangerously experimental world of "unstable".
That said, one of my boxes is a FreeBSD 9.0 "current" machine just because I couldn't get perforce access to pull a driver I needed into 8.0 (what a crap system perforce is, by the way) and it's worked absolutely flawlessly.Edited by ghell - 5/18/11 at 3:42am