Hello, Berserk, you wrote: N>> Upon - it was accelerated. But there simultaneously and in large quantities the interior of many functions has been rewritten on SSE, AVX, NEON. Well that is it was accelerated not at the expense of a rewriting on With ++? No, not for the account. I also did not write, what for the account, you track conversation? I cannot still understand, how it was affected by a C ++? With ++ made possibility sharply to expand library with functions and algorithms, thus its usage became easier. Earlier the main data type was ugly IplImage with as which was to work inconveniently. Now it cv:: Mat (and not only, there a little different Mat). Not not clear cvSeq, and std:: vector. Etc., etc. Smartpointery, interfaces, templates, an overload of functions. It was necessary to write a heap the service code earlier, and began to describe probably practically only algorithm. And after passage on With ++ the active growth of library began, it became de facto the standard in the field of computer sight. Also it is an indisputable fact - Khronos in the standards refers to it too. Further interiors of functions actively correspond on SSE, AVX, NEON. The Nvidia by own strength does CUDA-versions of the majority of algorithms, Intel and by own strength - OpenCL versions. Also the Nvidia does under Tegru. It is all happened on my eyes, I used OpenCV from versions 0., something , something found and spoke to developers. And so before passage on With ++ the library was a hand-made article from Intel with memory leaks, and after passage on With ++ became almost the branch standard. And even IPP it was practically bent on its background and now it is offered free of charge as acceleration of some parts OpenCV. There and then: ccv, written on With, it was bent, though contained very fast implementations of many popular algorithms. The library dlib - this already on With ++, develops, in many areas competes with OpenCV. So in this area From library on all fronts gives way With ++ to libraries. As a whole it seems to me Pzz the rights about that what critical things on runtime it is necessary to write that in procedural style with usage of own data structures specially optimized under the task. In such approach, most likely, many possibilities With ++ will not be used. And I think that is not right. With ++ with its templates gives free abstractions, which frequently also faster. A vivid example - functors instead of pointers on function. Plus is more many enough difficult things, type of stabilizing of video. It something of type which comprises a call of several algorithms (driving search, driving model, compensating, warp and fuse - I do not know how correctly to translate). And all these families of algorithms have a set of implementations, each of which depends on a dial-up of the parameters. And on With ++ the code using stabilizing, looks compactly enough and beautifully. ON About the same code was before bulky that the eye was simply lost in details, it was very difficult to make out algorithm behind a heap of a tinsel. Here in such places very often also there are errors. Or behind complexity of implementation the algorithm essence is lost. It would be possible on With to write it better? Yes, it is possible. But then it should to do manually all that already is in other language which on all fronts turns out better.