For an open source project with a very small developer pool, it can cause the project to actually die off. We spent a large amount of time on support for something which didn't apply to well over 80% of our user base. Let me explain this a bit further, and how we came to this decision. Over 80% of our userbase that hits the website is on 10.6. 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.ģ) A userbase which for the most part moves with updates.
Please bear in mind that we have 3 real problems to address here in order for any sort of ppc support to return:ġ) Nobody who actually works on perian likes working on this old stuff.Ģ) A lack of time resources. We're just not going to continue supporting it in 1.3 (or whatever version number I end up being happy with). 1.2.2 and 1.2.1 will still work in 2 years if they still work today. 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.
XP is still supported by nearly all developers a decade later while Mac developers dump support for an OS version that is barely two years old.PATHETIC).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. It seems developers cannot wait to dump support for older OS versions regardless while Windows machines from 1999 can still run nearly all new software within their CPU capabilities speed-wise (i.e.
0 kommentar(er)
