Is the performance issue with the parent argument in Instance.new() fixed?

[VSCPlays (Reko_FromSlovenia)]

1. What do you want to achieve? So I randomly found an Public Service Announcement from 6 years ago convincing users to stop using Instance.new() like this: Instance.new("Part", workspace) for performance issues, and this is the one I found

2. What is the issue? It’s been 6 years and I’m wondering if it has changed as I mainly use the Parent argument in Instance.New() to make the code less messy

3. What solutions have you tried so far? I looked everywhere but didn’t find any statement from anyone

-- How I use Instance.new()
local part = Instance.new("Part", workspace)
part.Name = "BasePart"
part.Material = Enum.Material.Glass
part.Transparency = 0.5
part.Size = Vector3.new(2048, 1, 120)

-- How Roblox wanted us to use Instance.new()
local part = Instance.new("Part")
part.Name = "BasePart"
part.Material = Enum.Material.Glass
part.Transparency = 0.5
part.Size = Vector3.new(2048, 1, 120)
part.Parent = workspace

The Code I showed isn’t a part of what I’m working on, this isn’t a part of a plugin, a script or anything, it’s just an example of how I do it and how roblox expects us to do it

[msix29]

Nope, they haven’t changed it, adding an extra line won’t be so problematic so just go with it.

[VSCPlays (Reko_FromSlovenia)]

so it’s not changed for 6 years??? why didn’t roblox improve performance with the parent argument for such a long time???

[msix29]

Weird it’s the same for all that but what can we say.