fgarcia/gist:2d386a6ddd273229d113

## gistfile1.txt
Listening to Ruby Rogues I heard one of the panels claiming performance problems because too many objects where created on every request:

http://devchat.tv/ruby-rogues/186-rr-the-4-rules-of-simple-design-with-corey-haines
(Search for: immutability)

I was curious since I started using DDD patterns the number of classes and temporal objects have exploded.

The speaker mentions "a ton of new objects for every request", so I assume that "a ton" is about hundreds or thousand of objects within a large loop, long running loop, nothing to be concerned if it is just a linear sequence of actions for a response.
	Listening to Ruby Rogues I heard one of the panels claiming performance problems because too many objects where created on every request:

	http://devchat.tv/ruby-rogues/186-rr-the-4-rules-of-simple-design-with-corey-haines
	(Search for: immutability)

	I was curious since I started using DDD patterns the number of classes and temporal objects have exploded.

	The speaker mentions "a ton of new objects for every request", so I assume that "a ton" is about hundreds or thousand of objects within a large loop, long running loop, nothing to be concerned if it is just a linear sequence of actions for a response.