As my name was mentioned.
If someone has had problems with FTMM it is probably sufficient if they have move on to say that moving has/hasn't solved their problems.
As it happens I tried MacFamilyTree, and whereas it was much better than FTMM it was, for me, not adaquate. Reunion solves most of problems, but I still suffer from the odd crash and miss some of the FTMM features.
This is an experience for consideration by anyone who is having problems that no one can suggest a solution to or is unable to put up with.
If discussing the operation of FTMM, it is not unreasonable to compare the slow loading of FTMM with the almost instaneous loading of say Reunion.
Again on memory usage, if FTMM is gobbling memory, the fact that Reunion is very economic.
And so on.
The question underlying it all, is this a problem of the coding of FTMM,has speed etc been sacrificed for something else or is it a money problem?
As for posting elsewhere, there is a proper developer monitored board rung by Reunion which I read. Leaving aside the fact that problems seem to be limited, I cannot say that I have seen anything that I could contribute to.
Although my experiences of FTMM are getting old, I do have extensive experience of working with a larger database and if I can help someone with a problem related to that I will do so.