When teaching I've always emphasised certains aspects of the UI that are consistent and can be relied on. Good UIs generally are also very consistent.
UnityPlayground makes the Unity UI objectively worse in one respect by changing the usual behaviour of numeric fields in the Inspector.
"Hey everyone - notice how you can change values in any number field by dragging with the left mouse button over the label? That's often a really good way to change values and see the results immediately"
"Please sir, why doesn't it work in for Transforms?"
"Erm. It will do on normal Unity projects but for reasons I don't want to go into right now, it doesn't work if we're using UnityPlayground"
I know it's a small thing but it's the kind of thing that chips away at students ability to form a nice mental model of how the software works.
When teaching I've always emphasised certains aspects of the UI that are consistent and can be relied on. Good UIs generally are also very consistent.
UnityPlayground makes the Unity UI objectively worse in one respect by changing the usual behaviour of numeric fields in the Inspector.
"Hey everyone - notice how you can change values in any number field by dragging with the left mouse button over the label? That's often a really good way to change values and see the results immediately"
"Please sir, why doesn't it work in for Transforms?"
"Erm. It will do on normal Unity projects but for reasons I don't want to go into right now, it doesn't work if we're using UnityPlayground"
I know it's a small thing but it's the kind of thing that chips away at students ability to form a nice mental model of how the software works.