Question re AI(vibe) coding and a new engine
Posted: Thu Nov 12, 2026 11:07 am
First, huge thank you, Daniel (and all others involved) for CloudCompare. I've used it for so many projects over the years. It fills a huge void in the world of point cloud software.
If I were to vibe code a new app that swapped in a new engine for loading, data management and rendering, and ported over all the functions from CloudCompare, where would that fit? It will obviously be a nightmare from a code reviewing perspective, but at the same time, would resolve some of the issues acquired over CloudCompare's long heritage (large point clouds with panoramas being a good example). It would obviously have to follow all licensing requirements.
Could such a development live in CloudCompare's github on a branch as a great big contribution, or would you rather it stay out? As a more general discussion, where does AI coding fit into CloudCompare's current and future development processes?
If I were to vibe code a new app that swapped in a new engine for loading, data management and rendering, and ported over all the functions from CloudCompare, where would that fit? It will obviously be a nightmare from a code reviewing perspective, but at the same time, would resolve some of the issues acquired over CloudCompare's long heritage (large point clouds with panoramas being a good example). It would obviously have to follow all licensing requirements.
Could such a development live in CloudCompare's github on a branch as a great big contribution, or would you rather it stay out? As a more general discussion, where does AI coding fit into CloudCompare's current and future development processes?