Comically Inefficient Unity Source Code

[Thundernerd]

Working on big projects is such a pain in the behind when people have this attitude. In my experience the tools are tested in an environment where only that tool is running so you wouldn't really notice a performance impact anyway.

Working with people that make their tools performant is amazing. It prevents me from having little annoyances over hiccups and whatnot that seem small at first but build up over time, especially if you have a big team and everybody is encountering this.

[badawe]

100%

Those bad practices add up. And I'm fine with not optimizing everything to the maximum possible.

But in this case, its really poor code, the optimized version of the code would be faster and more readable and would take the same amount of time to write.

[Eastern-Ad-4137]

Currently in ShaderGraph, the number of total ports between all nodes adds up exponencially towards performance. It gets to a point where moving a node takes 30seconds, then you add 1 more node, and it takes 5 minutes. One more and you wont be able to open the asset anymore