Copypasta is evil

I declare copypasta and design patterns, save for very rare exceptions, are sign of a sucky programmer or a sucky non-functional language at work. Programmer editors should have an option to produce a warning when you paste more than two lines or 80 non-whitespace characters, telling you that you are doing something wrong.

When working with a decent language, and by decent I mean anything that allows you to barely work with dynamic functions, so anything from PHP counts, I can hardly think of a situation where you'd need to copypasta your code, let alone use a professional enterprise best-practices design pattern.

>>14
Not really, it's more like: I've been hearing people circle-jerk about design patterns for some time, and always wondered what was the big deal with them. Then I realized copypasta is bad, because anything you copypasta means you have to keep track of where you copypasted when you need to modify copypasted code, and I realized a good language always has ways to almost completely avoid copypasta. Then I went back to design pattern people and realized they are fucking morons for copypasting, and for circle-jerking to stuff they don't completely comprehend and couldn't come up with, because today's best-practices programming is about the "glue", i.e. a sub-par graduated programmer with no experience trying to figure out how to make Java shit work together in that shitty language.