You can't imagine that someone working on something like this would slow down as the work neared completion? Why must a piece of software / code constantly be changing? What's your specific concern? You're making a very strong claim that the "project has stalled" without any real evidence. Furthermore, the project "stalling" makes it less... what, exactly?
apetrov|1 year ago
Based on my experience (both personal and from colleagues), when a project is not in active development, the team starts losing knowledge of the codebase along with its context. For example, something that was at your fingertips while actively working on the project would be much more difficult to recall after a year. The difficulty of maintaining or extending the project grows over time if it is not actively worked on.
‘Stalled’ = contributions become less and less frequent.
If a project has stalled, there isn’t much new happening. For a simulation like this, the sky is the limit—you can make it as accurate as possible (e.g., accounting for light pressure - esp. significant around blackhole acceleration disk, the Yarkovsky effect, etc.)