If you can't even get a small record company (or small publisher, or SOMEONE with at least a little clout) to support your work, odds are there is a good reason for it.
Yes, because every author or musician should have to give up his copyright to some company, otherwise, you know, it must suck.
odds are there is a good reason for it
Maybe the new author doesn't want to have to give up his copyright just to be published? Maybe because old methods are dying and on-demand publishing will be important in the not-to-distant future?
So I would try to switch to KDE from Gnome for a while, but found the same issue where I would have to pull in/use a Gnome/GTK+ based app.
...Linux and OSX which run on several different and totally alien architectures.
Linux and OS X run on x86 just like MS Windows. I doubt Google will be releasing a PPC build for Mac or any of a number of other architectures available on Linux.
I agree with you about IPC not being the easiest cross platform thing to do. However, it is not terribly hard if you follow POSIX and wrap for Win32. As pointed out there are already cross platform IPC libraries like Boost and D-Bus, etc.
I have a legal copy of Office 2003 (which kicks OpenOffice up and down the road so hard it's not funny)
Huh? Have you REALLY used OO.org 3.0+? I am sorry but MS Office 2003 doesn't have anything over OO.org 3 from a normal user standpoint.
In contrast it has many features the MS Office 2003 doe not. The biggest feature for me is being multi-platform. I get the same consistant interface and features going from WinXP to Mac OSX 10.5. The best feature I love is to be able to export my final document to PDF and get a very good output result. I tried some plugins for MS Office 2003 to do the same and the output has just not been what I want.
From your personal experience, what can you say that MS Office 2003 offers over OO.org 3.0+? Or have you not used OO.org enough to offer an intelligent comment?
I too have a legal copy of MS Office 2003, not a biggie there. I have yet to find anything in MS Office 2003 that I personally could not do as well or better in OO.org 3.0+.