Objective C / C++ is only required for doing the UI. 99% of your project can remain in C or C++ with only a very thin shim in Obj-C for the UI layer. There is no requirement to move your code base to except for the Mac-specific UI layer.

There is no 64 bit Carbon, because it's a relic. Cocoa easily mixes with C code (Obj-C is just C with extra stuff). Unless you're Adobe and you have a huge amount of UI code in Carbon, there is no reason to keep hanging on to it.

Grand Central Dispatch is not required for video at all. Mac OS X supports the standard POSIX pthreads interface for threading.

I run Linux, where's my ZFS? No, FUSE doesn't count.

x | ~x = 0xFF..FF, which is equal to -1 in the 2's complement signed version of the resulting type. Why not (0x2B | ~0x2B) == -1

example:
    main() { printf("%d\n", (0x2b | ~0x2b)); }

No, it's GNU/FreeBSD. It can, however, emulate Linux system calls and therefore natively run binaries compiled for Linux.

I recall Fake Steve Jobs had some rather insightful thoughts on this.

What's wrong with Objective C? You can mix Objective C and "pure" C / C++ in the same project. Any decent C++ programmer can pick up Objective C / Objective C++ in one day of practice[1]. Obj-C is a superset of C, all of your favorite tricks still work. You can program it on Linux or Cygwin using GnuStep and gcc (though admittedly getting it going is kind of a pain). If you really hate it that much, you can get away with writing a pretty thin wrapper of Obj-C to interface to the OSX specific APIs (most of your calls will probably be standard libc calls in C anyway), and have almost all of your code in C/C++. I don't see how it would be an obstacle to anyone.

[1] No True Scotsman would doubt this comment.

I did some research into this a number of years ago (before torrents were around). I found that you can store 64 KB (if I recall correctly) in a slashdot comment. Now, the idea was not to to use slashdot as storage, they'd quickly put a stop to that. The trick is using slashdot and other forums and wikis as a way to get your data into the Google cache, where it will be served rapidly for everyone who wants it. There should also be forward correction data uploaded (like parity files) so that if some segments get lost, they can be recovered. Then what you need is an index file (kind of like a torrent file) that tells you what Google keywords you need to search for to find any given segment of the file, and software that will parse this file, download, and assemble the chunks into the completed data.

I wrote a little bit of code for it. It's all very straightforward, I just never got the time to get enough of it implemented to release anything. With torrents, it seems somewhat worthless to pursue now.

Stop right there. Sun is one of the biggest corporate contributors to open source. Go ahead, count lines of code. I'm betting Sun will be in the top two if not #1.

Here's a brief list of things Sun has open sourced:
Solaris - Their entire OS, including ZFS and Dtrace
SPARC - Their CPU line
Java - Maybe you've heard of it.
OpenOffice - The office suite that ships with every desktop Linux distribution.
VirtualBox - A GPL desktop virtual machine.
NetBeans IDE - A multi-platform IDE.
OpenDS - LDAP Directory Server
High Availability Cluster

Honorable mention:
NFS - The Network File System
vi - developed by Sun founder Bill Joy
MySQL - Now owned and maintained by Sun-paid engineers

So, next time you say Sun hadn't done much for open source, look again. It would be a shame if Sun was bought by Oracle and all of their valuable contributions were abandoned.