You only have to pay if the repositories are private.
Interesting, the report specifies that user data is 1 of 3 types:
I wonder if it could be something like "derived" or "deduced" data, which is information about the user obtained from other sources.
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."
This is true. In After the Gold Rush Steve McConnell makes the point that "Software Isn't Soft" (p. 19):
As software systems have become more complex
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.
Three words for you: Virtual Private Server.
All the control you'd need, and none of the hardware maintenance.
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.
It's true that SVG can scale, but you need tailor them for the intended pixel size. SVG images designed for 256x256 look horrible when scaled to 16x16 or 32x32. The smaller ones need less detail, so you can't just assume that an SVG graphic will work at any resolution.
Just look at the greasy finger marks
The question of smudges was addressed by Zach Pace in the Building Windows 8 blog entry on picture passwords. He emphasizes that Microsoft's goal was to design a password mechanism that was easier to use than PINs on touch devices, with equal or better security.
The picture password system is certainly vulnerable to the smudge factor, but it's no worse than existing PIN systems today.
It doesn't affect the obese? (runs)
I see what you did there.
"Consistency requires you to be as ignorant today as you were a year ago." -- Bernard Berenson