@
DerekCuster
I have no intention of starting a debate or continuing any debate/argument that is in progress, but I am bothered by your assumptions that are based on Team XBMC "titles".
Being a developer or not doesn't necessarily mean someone understands the topic of color space. Nor do the titles under our usernames strictly define what we do. For example, I do more than just things on the XBMC Wiki, but I put my little title as "XBMC Wiki Guy" to encourage people to ask me if they have any wiki related questions.
I don't know Martijn's resume, so I can't tell you what he does or doesn't know, but I can tell you that if he mentions something then it's because he understands that topic, and that what he says can be trusted to be correct. You'll find this is true for just about everyone who's a member of Team XBMC (there's a lot of members, and I haven't met them all, but this is true for the ones I have met).
Even if he or any one else on Team XBMC is mistaken about something said, that doesn't justify the disrespect you've shown Martijn. I understand that this topic has gotten a little heated (and I've lost my cool on the forums before too), but going forward, please keep this in mind. Remember, the first step in getting someone interested in working on something for you is to not piss them off, or piss off their friends :)
@all
In the relatively short time that I've been a member of Team XBMC, I've learned that the members/developers are incredibly diverse. While I think some of the frustration expressed in this thread by Team XBMC members is very justified, in general people should know that one or even a few members don't necessarily represent the group's mindset. Especially when it comes to what ideas are developed and picked up.
I often tell people that they shouldn't really hold their breath when it comes to features that will only effect the minority, but I don't say it will never happen. Far too many times have I been surprised at what someone has taken interest in and developed in XBMC. How many users something effects is simply something that
might play a factor in a feature being adopted or not. We typically say these things not to discourage users, but rather to not give any false hope. Nothing seems to piss off users as much as a promised feature that doesn't work out in the end :)
If anything, it's a rough way to gauge how likely we are to have a developer (or get a new developer) who is interested in working on that feature. Developers might consider popular demand when it comes to choosing what they work on, but most often it really just comes down to what they wish to spend their time on.
