No, MLO is deeply flawed.
In many ways MLO is brilliant - massively configurable and very good at doing various things. I 'lived there' recently for about 12 months.
However from a GTD perspective the deep problem in MLO there is no field for Area of Life and no field for action status (Waiting, Someday-maybe, Active etc) . And there are no spare fields that can successfully be used as such. And given the fairly high number of tasks that I had on the system (including 'Somedays' I usually have c. 400 -500 tasks)... every single workaround I tried had nasty unintended consequences.
By the end, The Monkey's Paw kept coming to mind!
I must have tried about 8 fundamentally different ways of structuring my data and trying totally different workarounds, but in the end the problem with MLO is that it's database architecture is fundamentally screwed for GTD use.
Coming from MLO, what is particularly refreshing about TDL is the number of data fields, and the ability to set up your own and even define various things about them (e.g. type of list etc) is a real breath of fresh air.
Unlike TDL, MLO also fails to let you control what fields 'inherit' from parents.
I participated quite a lot in the MLO forum, but the developers themselves were extremely unresponsive, and also had very VERY slow iteration times. Moreover most of the other users seemed to shudder at yet more complexity being added to an already confusing and cluttered interface. So eventually I was forced to jump ship.
J