TweenService should have functionality for non-instance values

You are absolutely correct. Don’t expect other developers to follow the practice though.

From our discussion this seems more opinionated than anything, and I don’t want to continue down that rabbit hole which doesn’t result in anything constructive/helpful. Regardless of which approach is “better”, we’re still going to see custom tweening libraries (e.g. Crazyman’s) from developers who don’t want to use Value* objects for tweening. Now that both angles have been made, I’ll leave it up to the ROBLOX engineers to decide what’s best for the platform.

1 Like