Re: ReaderWriterLockSlim + Dispose?

Tech-Archive recommends: Fix windows errors by optimizing your registry

I got a relation to Mac and Nazi in one post, your looking evil now,
wuahah.

It is not true that "Money = Performance".

In a metaphore or analogy, it can mean anything I want as long as the
persons smart enough to pass those classic IQ tests (_ is to _ as _ is
to _). Else I have to spoon feed it to them... which isn't as fun.

People think in different ways than others. Forcing someone to write
code in a certain way will only prologe the development process. If a
person wants to dispose straight away and let threads do their thing,
then thats just the way he thinks. For small classes it might even be
the best way IMO. I'd like to see your proof on this method taking
longer/cost more to develop, but I think we both know there isn't any
(expecially if the developer already has that solution in his mind...
you want to force a different thought process into this guys head with
no "good" reasion as I can see). You agree performance wise it isn't
worst, you seem to think it'll be harder to maintain which isn't true
either - as long as its commented right it'll be just as easy as any
other implementation. You seem to think it'll take longer to develop,
for some maybe, the reverse is true for others.

Now if you were giving valid reasion's, even I'd convert and say "oww
definally want to do it that way, I see why now", but the "nope, the
design is flawed because it's not the way I do it. You way works just
as good, but costs more to develop." is a very hard argument stance to
succeed in.

NB
.