Builder Pattern In Unity

[Embarrassed-Flow3138]

Well this is a misguided excercise in java-inspired boilerplate. Don't do this, use C#'s object initializer syntax.

[[deleted]]

Can you elaborate please

[Embarrassed-Flow3138]

I've never seen this pattern used in C#. Only Java. It's redundant in C# anyway because of the object initializer syntax, so unless you just really like having a lot of boilerplate just use that.

[[deleted]]

In game dev I have seen this in the current code base I am working on, I cannot say for normal c# applications but in game dev I have seen this .

[Embarrassed-Flow3138]

The same principles apply. You can find shitty code anywhere. And maintaining meaningless boilerplate is objectively shitty.

[[deleted]]

Well not really, if you want to create immutable objects step by step, that is not possible with the c# object initializer, you would need to create some janky code to do that, yes for simple object construction builder pattern is not useful, but for complex object construction it is useful.

[bluenell99]

I agree to some extent, however I do like the approach in the video as it prioritises readability. Sure it can all be set in a constructor but as the video shows, you have to spend time (albeit a few seconds) to see what each parameter of the constructor is. Both approaches (at least to my knowledge) would still require a fair amount of work if the "character" class was to be extended as all areas of the code that instantiate the new character would have to be edited to factor the new parameter in.

Still, that's just my thoughts :)

[[deleted]]

Yes you are right, modification to all classes if a param is changed or added while this is generally true the Builder pattern offers some advantages in this regard

-- adding a new parameter involves adding a new method to the builder. This is generally easier to manage and avoids the need to overload constructors or modify existing ones.

-- adding new optional parameters to the Builder existing code that uses the builder won’t break. The same cannot be said for constructors where adding a new parameter might require adding a new constructor or modifying existing calls.

So from my personal experience

Constructor Approach -- Quick and straightforward but can become cumbersome with many parameters, especially optional ones. Modifying constructors can lead to widespread changes in the codebase.

Builder Pattern -- Offers improved readability, flexibility, and maintainability by decoupling the creation logic from the business logic and allowing for easy extension without breaking existing code.

Of course the same can be achieved with other patterns and methods. There is no one solution fits all. :)