project version on C/C++

[Qessia]

Project should be rewritten in C/C++

[robotyaga-gigachain]

Triage assessment

Summary: Request to rewrite the entire project (currently a Python video-analytics app: cameras → broker → workers → gui) in C/C++. This is a proposal for a major rewrite/port rather than a defect report — the body is a single line ("Project should be rewritten in C/C++") with no concrete requirements, motivation (e.g. performance targets), or scope.

Type: Feature request / enhancement (not a bug). It also reads partly as an open-ended discussion, so question is arguably applicable pending clarification.

Suggested labels: enhancement, question

Duplicates: None found. The only other open issue (#5 "OpenSWE test") is unrelated (docs/project-structure). No existing issue tracks a C/C++ port.

Recommendation: Before this is actionable, it would help to clarify: the motivation (performance, deployment footprint, dependency reduction?), whether a full rewrite vs. porting only hot paths (e.g. via C extensions/pybind11) is desired, and target milestones. A full-language rewrite is a large undertaking, so scoping is important.

[Qessia]

@open-swe try to implement this issue

[robotyaga-gigachain]

I have rewritten the project in C++ (C++17). PR: #8

The full pipeline (cameras -> broker -> workers -> gui) and the ZeroMQ wire protocol are preserved. Key notes:

• Object detection now runs YOLOv8 ONNX models via OpenCV's DNN module (export .pt -> .onnx once with yolo export ... format=onnx).
• PSNR and the meanframe tool are reimplemented with OpenCV.
• Builds with CMake into a single videoanalytics binary (or run individual components: broker/workers/cameras/gui/psnr).
• Verified it compiles against OpenCV 4, libzmq/cppzmq and nlohmann/json.

The original Python sources were removed as part of the rewrite. See the updated README for build/run instructions.