setter

Much more than a static credit - the music is also a fantastic mood setter in this case.

Mechanical Turk, for example, the price is (rightfully) set by the problem setter.

This is all not to mention that since the setter is public, you don't have any protection of your internal data structure anyway since anyone can modify it.

Using setter DI, which normally compromises the design even more, to supposedly make the design better is suspect.

And particularly Paul, as popular as he is, should be real carefuly about his opinions, because he's a trend-setter.

In this case, you're using String#gsub as a setter for the port attribute of a URL masquerading as a string.

You could also make magic getter/setter methods if you really wanted to get crazy with it.

You can take a lock in your setter, to ensure that the passed information is applied in a thread-safe way.

You can check invariants in your setter before applying any changes, and throw an exception if the passed value violates them.

I usually dislike setter methods, since it becomes hard to track all the places that modify the state.

You have a class that is being created from a few places and add a new dependency via a setter to it.

You run a thousand different micro-benchmarks on the performance difference between re-binding a cached method handle for a setter, or just calling instance_variable_set.

The Egg is quite versatile in that you can do direct grilling along with indirect slow roasting, by use of a "plate setter".

Setters basically send a signal to the developer that the dependency is "optional", since someone can create the object and simply not call the setter.

Microsoft is a trend-setter and whatever the reasons behind this "opening" it really sets a powerful precedent for future projects getting open-sourced by companies...

"Microsoft is a trend-setter" I would say "was".