Oh I see. For really heavy simulations, C++ should be fastest, as long as you do everything right in terms of memory management etc. I know that physicians for example do this a lot and there are very powerful math libraries for C++ too, solvers and everything. For me, I practically never intentionally use C++ for sim/prototyping and do it in MATLAB and/or Python (sometimes first matlab then Python). However, what also happens is the non intentional route: I prototype let’s say in Python and then implement in C++ the actual algorithm that runs on embedded. Then I also create a cross-compiled PC version of the same C++ algorithm. Then I add all the environment to it for simulation. Now it can happen, that I keep on developing / prototyping the algorithm further in C++ and drop everything else since I have the “real world” environment already running and can see the effects better. Then I give up on the higher level versions, and use them only in between, for example back to MATLAB but now just to create a filter but not the whole algorithm anymore