Based on that article, I think Ubuntu probably would push me away from the PC, too. I used a variant called "Goobuntu" (guess where...) during my tenure at one particular company, and it was a mixed bag. I'm not sure how much was due to Ubuntu itself and how much was from the local meddling, but it was wonky in ways my Linux boxes normally aren't.
Put it this way - my machine at work was some beastly multi-proc Pentium 4 something or other, and my machine at home was some random gunk I put together using old parts from Micro Center. It was so old, I had to special order the CPU online because nobody in town still had them in stock. I live in the valley, and could drive to AMD in under 15 minutes. That's just nuts.
Still, my machine at home was far more responsive than my workstation ever was. There were tons of weird glitchy times where it would just sit there and lag for no apparent reason. I didn't even get the worst of it, since I ran a minimal window manager. People who went for the full-on "desktop environment" (KDE? GNOME? whatever it was on that distribution, I don't know) had even more anomalies.
When I hit my hotkey to pop open an X terminal and don't get my shell prompt in a blink of an eye, something is very wrong.
Edit: forgot something. My home machine was faster over my cable modem + ssh tunnel to work than my work machine was sitting on the corp gigabit Ethernet. Think about that.
> Still, my machine at home was far more responsive than my workstation ever was. There were tons of weird glitchy times where it would just sit there and lag for no apparent reason.
I never worked for Big G, but I've felt that exact pain before--that sounds like the classic "enterprise diskless workstation problem." Lots of big companies like to obviate reimaging their Linux boxes by just mounting /usr over NFS. Then, they don't fan-in correctly, so they have too few servers serving too many clients with too little disk locality between requests, so your request to read, say, a font from /usr/share/fonts has to sit in a queue.
Please, if you are a sysadmin who does this: just run a daemon which, in effect, rsyncs the system to the disk server instead. Your workstations have big disks, sitting around doing nothing. You can be as clever as you want, serving squashfs underlay images over bittorrent in the background and then switching out the rootfs link on download completion--just, please, do something other than NFS. NFS is meant for shared filesystems that change; it has absolutely no advantages for a shared read-only rootfs.
One significant point that you made in your original post was that you did your Linux upgrades on your own schedule to meet your own needs. This cannot be overstated.
I understand David Drake's issues with Ubuntu 12.04 with the bloated GUI that comes out of the box - but there are less problematic alternatives, such as Xubuntu. Still, he was right about the time he spent searching for how to fix configuration issues. I would love to hear his take 6 months after he has been on MacOSX if he uses it for serious coding outside of the Apple ecosystem. I use Homebrew on my MacBook Pro and do just as much searching for how to get some code to port because of idiosyncrasies in OSX. Still, I do like my 2009 MBP on Mountain Lion.
DIY is a great lifestyle. And it comes with many positive benefits, not least of which affect mood and outlook.
I'm typing this on a 7-year-old Thinkpad X60s, and with the right Firefox add-ons, surfing feels more responsive than on my (untuned, unoptimized) i7. The clunker is way more fun.
Getting something relatively "perfect" and finished is just not as fun as having something which needs a lot of fixing, assembly, experimentation, etc. If only for the feeling of control, transparency and understanding how things work, it's worth it.
Ubuntu is full fat and runs a lot of processes by default.
Once Canonical have the device drivers sorted for native linux on a range of hardware, there is nothing stopping anyone putting arch or slackware on the same platforms. Perhaps some extra gunk in the kernel.
Put it this way - my machine at work was some beastly multi-proc Pentium 4 something or other, and my machine at home was some random gunk I put together using old parts from Micro Center. It was so old, I had to special order the CPU online because nobody in town still had them in stock. I live in the valley, and could drive to AMD in under 15 minutes. That's just nuts.
Still, my machine at home was far more responsive than my workstation ever was. There were tons of weird glitchy times where it would just sit there and lag for no apparent reason. I didn't even get the worst of it, since I ran a minimal window manager. People who went for the full-on "desktop environment" (KDE? GNOME? whatever it was on that distribution, I don't know) had even more anomalies.
When I hit my hotkey to pop open an X terminal and don't get my shell prompt in a blink of an eye, something is very wrong.
Edit: forgot something. My home machine was faster over my cable modem + ssh tunnel to work than my work machine was sitting on the corp gigabit Ethernet. Think about that.