https://community.redhat.com/blog/2015/12/guidelines-for-announcing-software-releases/

It’s also important not to combine things when they shouldn’t be combined. There are times when combining two implementations into one would cause more complexity for the system as a whole or violate the Single Responsibility Principle. For example, if your system’s representation of a Car and a Person have some slightly similar code, don’t solve this “problem” by combining them into a single CarPerson class. That’s not likely to decrease complexity, because a CarPerson is actually two different things and should be represented by two separate classes.

АУТИЗМ [HD] [1080p] [WEB-DL] [Custom] [Чистый звук] (2016)

Do you want to see this fixed?
Are you willing to do the fixing yourself?
If the answer to the first question is yes, and the second is no, then you've just volunteered for the job of either community motivator, or frustrated user. The goal then is to make people care more about going out of their way to fix things than going out of their way to find ways to make you even more frustrated. Which do you think is going to be more emotionally satisfying to those who read this thread?

https://www.eff.org/deeplinks/2015/12/panopticlick-20-launches-featuring-new-tracker-protection-and-fingerprinting-tests

Новости за день такое дно, что даже копипастить лень.