Considering that while the x86 version of Haiku is the main concentration at this point in time, it may be advantageous to plan for the distribution of applications with multiple system architectures. I am thinking of mainly, (of course, inspired as an osx user), ppc and x86. Of course, this differs from the way Apple considers their "fat binary" system: as a hand outstretched from the future to the past.

The idea is that there is possibly a market for Haiku to appeal to: old ppc systems which logically are going to be increasingly neglected by Apple and its OS, which will now focus on their new Intel Architecture. They stand to gain from all of the performance and the small footprint of Haiku, and to the older PPC users it may remind them of the best parts of the experience of OS 9 (I used it, and BeOS to me always evinced just that).

So, lets make it easy for those of us on different sides of the architecture fence to walk forward together, and lets make it easy to collaborate together. Having a common set of tools is essential to doing that, and that naturally extends beyond the standard tools that ship with the OS itself. We ought to encourage cross-compatability from as early on as possible, so as to ensure that the haiku user base will not be divided between platforms.

Even if we cannot make this for R1 (I have to admit as of late I am unsure of the exact status of the PPC port), this will be a good feature to keep in mind if Haiku decides to support two or more platforms.