You only have to pay if the repositories are private.

Interesting, the report specifies that user data is 1 of 3 types:

• Log data (user activity)
• Account data (Users emails, settings, etc)
• Third type is redacted.. Wonder what it is

If the requirements really are constantly changing, Agile poses a very real risk of never producing a working product. At some point, you have to step back and say, "Okay, we're never going to have a working building if we can't decide whether we're building a house or an office building."

As software systems have become more complex ... [the] notion that software is easy to change has become on of the most pernicious ideas in software development. Several studies have found that requirements changes—attempts to take advantage of software's supposed softness—are among the most common sources of cost and schedule overruns.

Flexibility costs money up front. Limiting flexibility saves money up front, but typically costs disproportionately more money later. The difficult engineering judgement is weighing the known present need against the possible future need.

In fact I'm struggling to think of even one case where the name of a TLD actually is the best site in it's category?

They could have selected any resolution after basing icons and other graphical bits on SVG and it would ALWAYS look as sharp as it needs to look.

Just look at the greasy finger marks

It doesn't affect the obese? (runs)