[Note: The thread was moved to Development chatter]
So the natural question that came to my mind is, has any of our coders thought about totally recoding MPT, using its important functions to do what makes MPT great? Is the enormity of the project greater than the time that the devs have? What has been the discussion so far?
Personally I would be rather strongly against rewriting ideas without been given very good justification. A few thoughts about this:
-It would be very time consuming and would need a lot of expertise which few hobbyist developer have. And if there were competent developers at every corner, I'm sure OpenMPT would have more skilled lead dev at the moment.
-There are no one working on OpenMPT code full time; implementing such huge changes doesn't sound like a thing that many would do just for 'fun' besides day job.
-Would the rewrite project ever finish? My not very glamorous view of many open source projects is that eager people start implementing some unrealistically large plans that just fade away because they have better things to do. For example history of Psycle is rather interesting to read from this perspective.
-Uncertainty on the result. After spending a lot of time rewriting the code, what would be the result compared to that situation that the same time would have been spend on developing new features on the old code basis?
What Jojo said. The version number doesn't necessarily
mean the bug was introduced in that version, it simply means that whoever found the bug was using that particular version.
Indeed, I took a quick look at .52 bug reports -- none seemed to be new to .52.
In my experience, the latest version has (with some eceptions...
) always been the most usable one.
In case you remember, what would be the exceptions (besides .50)?