I'm finding most of the example projects from the resources section of Unity's website do not compile and therefore can't be run. Is it meant to be an exercise for the developer to fix these bugs? Or should we fallback to Unity 2.x? Is it just me having this problem or are others having it to? Is there a workaround? I'm using a Mac OSX Leopard. Thanks.
I do not believe this is a problem personally. The new compiler in 3.0 is more scrict fortunately so some scripts that worked in 2.6 will not work in 3.0. You will find most of the errors are simple fixes such as dynamic typing changes, so fixing them takes little time.
You don't need to fall back on 2.6 unless you absolutely need one of the example projects, AND your programming is so bad that you cannot figure out how to fix the errors, and most of them, the console will make very clear what you need to do to fix it.
I don't know if the developers will go back through and fix the example projects, I wouldn't be surprised if they do, but it is not a pressing issue for most people, so there is no hurry on their part.
It is indeed planned to go through all the examples on our web site to make them work with Unity 3.0, but until that is done, we spent a lot of effort into making project updates from 2.6 to 3.0 as smooth as possible, so in most cases, as Peter said, fixing the projects should only take a minute or two.