From: Antonio Malcolm <antonio...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Decent Starting Point For Rolling A Desktop Environment?
Date: Tue, 3 Feb 2015 16:38:08 -0800 (PST) [thread overview]
Message-ID: <f4ea77a5-40b4-4897-88d8-1274d9bd6c5d@googlegroups.com> (raw)
In-Reply-To: <9386866b-d729-4587-bd55-ab639a2da6ed@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 3074 bytes --]
That's odd- I've always experienced the opposite, ie: the proprietary
Nvidia driver has typically worked for me, and the open source Nouveau
driver has typically given me issues.
Also, I've always needed to do some finagling to get ATI drivers to work,
but that's likely because I've typically installed my Linux rollouts on
Apple laptops, and dealing with their combination of GMUX hardware/GPU
hardware configuration and non-standard UEFI implemenation is a pain in the
arse, and has required rolling a kernel (of course, it didn't help that I
was running Debian, which uses an older kernel), and telling it where to
find the Radeon BIOS. Add to that, on my 2011 MBP, vgaswitcheroo works, but
something in the way MBP-specific GPU switching in the kernel extensions is
written (and the code, written by some guys at Red Hat, looks like it was
written a decade ago) causes the Radeon to crap out during subsequent
power-cycling (works the first time, not on additional tries), so I ended
up writing my own user-space utility for handling that.
From what I understand, the proprietary Nvidia drivers are better,
especially performance-wise, than the proprietary ATI drivers, and, from
dealing with both, I feel like Nvidia provide much more love to the Linux
community than ATI. This may be partly because a lot of high-end animation
and rendering workstations use Nvidia workstation-class GPUs for their
crunching, and much of that software is either Linux-native, or comes with
a Linux version (Maya immediately comes to mind), and Linux is used fairly
often in those scenarios. Admittedly, that's a bit of speculation, on my
part, but it's based on honest observation (I know folks in those
industries, so I have that as a starting point, at least).
Anyhow, GPU support is one of the biggest pains in the arse I deal with
during a Linux install.
However, there are definitely the other reasons I gave up on Cinnamon and
went with Openbox and Compton. That Cinnamon overrides certain Xorg
configs, and absorbs others in odd ways is the biggest. Conflicting with
the GPU driver was sort of the last straw.
I was using Linux as a server/hosting OS, mostly, and OS X as my *Nix-based
desktop. I got tired of the bloat and half-baked features, which, over the
last few revisions have stepped on my feet more and more and more.
I want lean, I want out-of-my-way. I find KDE to be incredibly bloated, and
both KDE and XFCE have wayyy too many settings panes/apps for my taste.
Most of that is stuff I'd typically set in a config file somewhere, and
touch maybe once in a blue moon- i.e., I don't really need a GUI for most
of it. I don't particularly care for the look and feel of either LXDE or
MATE, and I'll stay away from GNOME for the same reasons I dropped Cinnamon.
My current Openbox stack is doing a great job. It's easy enough to theme it
the way I want, with lxappearance-obconf and the standard config files. It
simply obeys those, it's lean, it's reliable, and it performs well.
[-- Attachment #1.2: Type: text/html, Size: 3049 bytes --]
next prev parent reply other threads:[~2015-02-04 0:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:58 Antonio Malcolm
2015-01-22 15:07 ` Christian Neukirchen
2015-01-22 15:09 ` Enno Boland
2015-01-22 18:35 ` Antonio Malcolm
2015-01-22 21:02 ` Logen Kain
2015-01-23 3:04 ` Antonio Malcolm
2015-01-23 3:19 ` Logen Kain
2015-01-23 16:08 ` Antonio Malcolm
2015-01-24 8:27 ` Antonio Malcolm
2015-01-27 1:43 ` Logen Kain
2015-01-27 1:52 ` Logen Kain
2015-01-27 1:57 ` Logen Kain
2015-01-27 8:55 ` Juan RP
2015-01-29 0:55 ` Antonio Malcolm
2015-02-02 21:35 ` Antonio Malcolm
2015-02-03 9:46 ` Logen Kain
2015-02-03 9:58 ` Stefan Mühlinghaus
2015-02-04 0:38 ` Antonio Malcolm [this message]
2015-02-05 10:39 ` Logen Kain
2015-02-09 18:56 ` Antonio Malcolm
2015-02-11 9:06 ` Logen Kain
2015-02-11 20:36 ` Antonio Malcolm
2015-02-04 7:47 ` Stefan Mühlinghaus
2015-02-04 18:34 ` Antonio Malcolm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f4ea77a5-40b4-4897-88d8-1274d9bd6c5d@googlegroups.com \
--to="antonio..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).