[Libav-user] Would anyone find an OS X / Cocoa / Swift wrapper for Libav useful?

[Brad O'Hearne]

> On Jan 27, 2015, at 2:52 PM, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:
> 
> But please do not expect
> everybody to agree

I didn't post the original message looking for agreement (and it doesn't bother me a bit if anyone does) ...I was trying to gauge who might be interested and whose specific use cases it might help. Disagreement wasn't the issue. Being rude and uncourteous and hijacking a technical discussion to throw out personal barbs and air personal politics is what I object to.

> and please don't try to convince 
> everybody what a great idea it is (I have doubts).

I already know it is a great idea, and that isn't because it is mine -- it is because of of spending 3 years with the FFmpeg myself; having clients who want a more supportable situation and don't want the uncertainty and risk FFmpeg inflicts on their projects; and because of those who contacted me off-list after I posted code to Github a year ago. The need and merit of the idea isn't even debatable -- perhaps you or someone else doesn't personally have a need for it, but others absolutely do. 

> (This is probably the moment where I should try to 
> convince you how futile your attempt is - NIH, 
> maintainability and complexity come to mind - but 
> this is free software: Please do it and prove me 
> wrong!)

No fear...I won't be. If I move forward, I'll author a completely new API, not built on FFmpeg. Your turf remains unthreatened.

> If you think the documentation needs improvements

This isn't even debatable. It needs to be written by the authors of the code, not those trying to understand it. Posting tens of thousands of lines of code and then expecting someone else to understand and document it is absurd.

> If you don't like my (or his) attitude, 
> consider that we are doing this in our free time, if 
> you still don't like it, there is no easy solution

How anyone treats another has ZERO to do with your "time", it has everything to do with what kind of person you choose to be and how you choose to treat others. And there IS a very easy solution: ditch the ridiculous "I'm a dev spending time on this and therefore I get to be rude" attitude and DON'T BE RUDE. People are rude because they choose to be rude people -- simple as that.

> this includes your note "I did 
> post code on github" (I fear nobody who reads this 
> list would download a software project to understand 
> a question)

Code was posted at the request of a dev. After it was posted, the same "too much code" gripe was aired, so I linked directly to the class and directed to the exact method which held the code in question: all accessible with a link in a web browser, no downloading needed. After posting that, then got the "devs aren't using OS X" and "devs don't want to read long emails" and "devs don't speak English very well" and "you're a troll for posting this and claiming it is doing X."

> : Simple and short questions are 
> typically much easier to answer.

Unfortunately not all problems come in a pocket-sized Jared jewelry box. I posted not only the code in question, but a fully runnable app with a UI to demonstrate the issue. I did all of this to a) get an answer to the questions for my client, and b) to leave no stone unturned, and c) to leave no doubt as to whether there was support available or not. No ambiguity remained.

> The idea was probably that people 
> like you who don't want to contribute but have some 
> understanding about the API help other users.

Once again, an intentional mischaracterization which which completely ignores everything I've written and the entire purpose for the original post to begin with: an attempt to contribute not only what would benefit my interests, but others as well. It's the same tired playbook: frame the person as the problem, question their credibility, kill the discussion.

Brad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ffmpeg.org/pipermail/libav-user/attachments/20150127/89b5e915/attachment.html>