If we could be sure something would work flawlessly then we wouldn’t need a beta feature!
The advantage of releasing something as a beta feature is that we can leave it available even if there’s some narrow issues. Like, imagine that the change broke one specific property that only about 1% of developers use. If it weren’t a beta feature we’d be forced to turn it off until we have a fix to not disrupt those developers, but as a beta feature we can just ask the small number of affected people to turn it off themselves while leaving it available for everyone else. This speeds up the process of finding and fixing narrow issues.
We’re also likely going to experiment with a couple more things as part of this beta feature. For instance, we may try moving the tags / attributes section to the top of the properties pane by default which is a big enough workflow change that we need to do it under a beta feature and get feedback.
I honestly think it goes good at the bottom on top of attributes. The bottom of the properties window is like “the instances custom settings” if that makes sense.
The alternative interpretation is: If you went to the trouble of adding custom attributes / tags on an Instance, that’s probably some of the most important information to know about the object, and deserves to be at the top.
But yes, being at the top isn’t always better which is why we haven’t pulled the trigger on that yet.
I just feel like it being at the top would be disruptive. Though I commonly work on scripts, I sometimes do UI. If these were at the top, it would be a much slower process to scroll down and change for example the color properties.
Maybe tags could do better at the top though, probably below the name and stuff.
The worry with that UX is that it’s unclear what your intent is: Do you just want to put a different tag on the selected Instances specifically, or rename the tag globally for the whole place?
