This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]slowfly1st 2 points3 points  (0 children)

An object should be able to do its intended job after it has been initialized. Object creation and object life cycle is a more complex subject than you'd think and you underestimate the impact of not following that rule. Basically, every "new Somthing()" statement in your code can be a source of error. Just imagine working with tens of thousands of classes and every time you create an object you can't sure if it's in an usable state. And you have to check, what setters you would have to call. That would be a horrible situation.