2014-04-24

About Windows OS

Last time I owned or used a Windows machine for any serious amount of time was in 2003. I spent some time as a full-time Linux user, both on desktop and laptop, and bought a used Mac laptop for home use in 2007, and a new one in 2009.

Today, I have successfully converted my home machine to run Windows OS.


I know. I am kind of perplexed myself. But honey, let me explain.

I've always believed in using open source software and supporting F(L)OSS projects. Stuff like that is what any community manager's dreams are made of. Mac OS has always felt like a poor compromise, but it had some Linux roots, and I could use the command line to get stuff working if something broke, and it wasn't Windows. Which was quite relevant back in the day when your choices basically were Windows, Linux, or Mac if you wanted to use a computer.

Today, most of my non-work computing needs are served by my Android mobile devices. I have a Nexus 5 and a Nexus 7, and a Nexus 10, and between them, they get me about 80 percent there. The only times I need an actual computer (like a laptop or a workstation) is when I need to input a bunch of text, do graphics editing, manage my music collection, or when I need to process orders from my racing numbers business.

With the limited use cases, comes higher pickiness about the tools. I can deal with slow when it's on a mobile device on a poor network. When my laptop slowed down to molasses speed following the Mavericks upgrade, I couldn't tolerate it. Something had to change.

Naturally, my first instinct was to install Fedora on the almost five-year-old MacBook Pro. Given the old hardware, I anticipated no real difficulties getting it to work, and hoped to get a couple more years out of the aging box.

My adventure lasted just a touch over four months and went about like this:
  1. Install Fedora 20, discover that the ideologically-pure distro has no support for my WiFi card (among other things)
  2. Spend an hour tethered to a wall with an Ethernet cable, find and install packages to run WiFi card
  3. Relocate back to comfy couch, realize the following things don't work right:
    1. graphics card (fuzzy screen, Steam games don't run)
    2. keyboard backlight (set to max, no way to reduce)
    3. screen backlight (set to max, no way to reduce)
    4. sound (microphone disabled each time after suspend)
    5. battery (system sees the percent charge, but suspends due to "critically low battery" at 80 percent anyway)
  4. Find and install Nvidia drivers, computer fails to boot into graphics mode. Rage-quit.
  5. Research why this is happening to me using my Nexus devices, boot into init3, remove conflicting Bumblebee packages, remove Nvidia packages, reinstall fresh from command line
  6. Enjoy brief victory
  7. Since I mostly do this after work, it's dark outside, and the screen set to maximum brightness starts bugging my eyes quickly. I try to find solutions for more than three weeks, while staring into a blinding whiteness of the screen.
  8. Stumble on solution to the screen brightness control after three weeks of running various Google searches and following links and leads from friends.
  9. Enjoy brief victory.
  10. Realize that keyboard backlight control still doesn't work.
  11. Get into the habit of keeping the "Sound" preferences window open somewhere at all times, so as to re-enable the microphone immediately after resuming after suspend. I use my laptop to answer Google Voice phone calls, so it can be challenging to have a conversation if you mic doesn't work.
  12. Strategically position power supplies around the house and only use laptop when connected to power. Get into habit of never using the laptop from battery power for more than 5 minutes.
  13. Realize that music management software won't work
    1. Banshee crashes self (and sometimes whole system) when I plug in my phone to sync music
    2. Rhythmbox doesn't crash consistently and throws an error for every single song synced via USB -- which is a lot of errors to acknowledge when you sync 600 songs.
  14. Endure ridicule from J. for putting up with all this. Somehow hold on to Linux love for another two months.
  15. Run one of the many system and software upgrades that Fedora provides, system will hang trying to boot into graphics
  16. One of later updates fixes that issue.
  17. Enjoy brief victory.
  18. Very next update kills WiFi drivers.
  19. Spend hours sitting on the floor tethered to the wall with an Ethernet cable trying to fix this. Fail.
  20. Wait for the next update for 3+ weeks. It doesn't come.
  21. Manually run yum update which fails to complete with no error.
  22. Rerun yum update and now  it says it needs to clean up. Run cleanup and attempt to update again, now it throws an error and says that any number of things could be causing it. Doesn't offer guesses as to what is wrong or how I could troubleshoot.
  23. All the while, sitting on the floor next to an Ethernet jack because WiFi doesn't work.
  24. Lose patience and install Windows 7. Have it up and running with native hardware drivers within one day. 
    1. Battery, WiFi, suspend/resume, screen and keyboard brightness, graphics card, all work, and...
    2. I can sync my playlists to my phone via WiFi again using a combination of iTunes and iSyncr.
  25. Sigh.
 So there you have it.

My logic is, if you have to compromise and use a proprietary operating system, might as well have one that works, which for given hardware neither Mavericks nor Fedora 20 could do. After my idealism has been tested for four months, I'm finding out that I'm a pragmatist after all.