Relja Ljubobratovic

I understand everything you're saying, and I have tried to design the API without the `Image` as intermediate class at first, but didn't like the way it turned out. If...

Yes, thank you. I was gonna make a whole FAQ page on the site to refer to such matters. That may take some time, so until that I should probably...

This is really complex topic, so let me start at the beginning. I recognized `mir.ndslice` as a serious opportunity for a scientific ecosystem to be established in D, as Python...

> Current DCV state is like python/numpy/opencv. It may be faster, but still useless for production I think its a lot worse than than - I'm pretty sure it's not...

> @ljubobratovicrelja I am sorry for the unrelated discussion No worries ;) always glad to see word of Mir spreading! > Algorithms should be nothrow @nogc. Delegates, associative arrays, classes,...

> Yes, we can use core.thread code and look into existing C libraries. Awesome, sounds good! How do we act with DCV until we have working version of such library?...

OK, great!

> Currently each major algorithm has its own API style, which is bad for big library Agree! This is something I really wanted to address to with everyone involved with...

There are no background extraction methods implemented, such as [this](http://docs.opencv.org/3.0-beta/doc/tutorials/video/background_subtraction/background_subtraction.html), but seems like it would be pretty trivial to remove black background in the example image you've given with DCV....

> (in ideally wepb, but D do not have native encoder/decoder :( ) Regarding this matter, my plan is to bind C libraries for image i/o, so if there's a...