In all fairness, if you can find a developer who wants to work on Perian on PPC, and can work with our very small team, then I'd be open to changing our stance.
With 2 very part time developers who actually have real jobs and real lives outside of this, and myself as project manager who has a real job and a real life, I really just don't see the point. 1.2.2 and 1.2.1 will still work in 2 years if they still work today. We're just not going to continue supporting it in 1.3 (or whatever version number I end up being happy with).
Please bear in mind that we have 3 real problems to address here in order for any sort of ppc support to return:
1) Nobody who actually works on perian likes working on this old stuff.
2) A lack of time resources. Did you know that we could have released in November if it hadn't been for supporting 10.5 and ppc? Not even 10.4, but 10.5.
3) A userbase which for the most part moves with updates. Over 80% of our userbase that hits the website is on 10.6. We focus on the 80/20 rule.
Let me explain this a bit further, and how we came to this decision. Essentially 2 and 3 are tied together. We spent a large amount of time on support for something which didn't apply to well over 80% of our user base. That's huge for any kind of software. For an open source project with a very small developer pool, it can cause the project to actually die off. No more perian < perian which is enjoyable to work on.
I can entirely understand your point. I have an old g4 800 mhz imac, I had a nice g4 ibook, a g3 700 ibook, and I had even older machines I won't list. The point is that we have to make the best choices for us currently, and for our users. I do respect older versions of os x and hardware, but not at the cost of what we're doing now.
I post this not looking for a response, but as an explanation. Concisely put, we have almost no motivation to continue working on 10.5 or ppc.
Chris Forsythe
Perian Project Manager