Legacy will vanish and will not be kept anymore (I read it)
is Mecanim a good idea to animate simple objects like an opening door or something like this?
a door opening does not need machine states.
This question is oriented to performance too, since Mecanim is not too cheap.
Opening doors can also be achieved by physics only. I created a script that is physics based to open doors and it tends to be very good in terms of performance. Check it out if you’re interested. I would only use animations for more complex objects but a door is just one simple movement.
Note: there is an update coming in a few weeks increasing the performance by a huge margin. The old script used the pre 4.3 Unity GUI system which is very heavy on performance. The code itself to rotate the door is lightweight.
You can use whichever you prefer; Legacy won’t be removed until we have a 1-to-1 replacement, at which time transition should be painless.
You can also use Mecanim mostly the same way you use Legacy (Animator.Play, Animator.Crossfade), using the AnimatorController as just a bunch of states.
As for performance; assuming you use mecanim and Legacy the same way:
Mecanim should generally be noticeably slower only if you have a lot of objects that animate once then stop, because mecanim writes every frame, even if a state has finished (because it’s a state machine), whereas Legacy soft-disables itself when a “once” animation is done.
Of course, if you add a lot of code in StateMachineBehaviours, or have every state connected to every other state, then that code has to be evaluated, but that would also be true if you implemented the same logic in Legacy.