Viewport Frame Parenting

[boatbomber (Zack_Ovits)]

@zeuxcg

Option 2 explicitly assigns Parent as the first thing, which is the worst pattern you can use. Consider the version of the code above with Instance.new called with parent argument:

local wall = Instance.new("Part", workspace.Effects)
wall.Size = Vector3.new(10, 10, 1)
wall.CFrame = CFrame.new(x, y, z)

You may think that this is faster because you saved one assignment, but it’s actually much slower in this case. Here’s what happens:

1. You create a Part with the CFrame of 0,0,0 and a default Size, and parent it to workspace.
2. ROBLOX sets up property change listeners for replication, rendering, etc.
3. ROBLOX queues a replication of a new instance with default values for the Size/CFrame
4. ROBLOX updates physics contacts between this part and whatever is at the origin
5. You set the part Size to 10,10,1
6. ROBLOX queues a replication change for the Size
7. ROBLOX updates physics contacts between this part and whatever is at the origin and overlaps with the part given the new dimensions
8. You set the part CFrame to x,y,z
9. ROBLOX queues a replication change for the CFrame
10. ROBLOX updates physics contacts between this part and whatever is at the position x,y,z given the size 10,10,1

Doesn’t it cut out steps 4,7, and 10? Aren’t those the heavy hitters?

I’m not arguing, I’m curious.