The firm dismissal was warranted in my view because he was trolling. Most of what he said was deliberate nonsense -- and he knew it was nonsense -- designed to provoke an emotional response. He even owned up to that here.
I owned up to no such thing.
I owned up to comparing you to the that guy because you used his exact words -- as soon as I recognized the words, I went ugh -- but I had to point it out because its a real weak argument -- but that got you to stop posting on the actual topic
looks wrong? DRY isn't about looks
Not all ideas put forth are accurate, and exploring them isn't trolling -- resorting to ad-hominem doesn't explain anything
Dave Thomas: Most people take DRY to mean you shouldn't duplicate code. That's not its intention.
DRY says that every piece of system knowledge should have one authoritative, unambiguous representation. Every piece of knowledge in the development of something should have a single representation. A system's knowledge is far broader than just its code. It refers to database schemas, test plans, the build system, even documentation.
Saying one version is shorter, more perlish, more clear -- that all makes sense
Saying its more DRY doesn't make sense
Saying the maintenance programmer goes ... thats a great topic if the exploration goes beyond "because I said so, you're a noob"