paulcam
Consider that Windows ships in over a hundred languages to hundreds of millions of people. I'm not sure how many languages Linux ships in (I'd bet quite a few), but Linux contributors don't have to worry about getting arrested for drawing map lines wrong: http://blogs.msdn.com/b/alexbarn/archive/2004/08/20/217602.a...
Do we ship software without testing? No. Do we ship software that isn't globalized? No. Do we just hack something together, check it in, and call it a day? No. These aren't the kinds of practices that lead to a stable platform.
Mistakes get made (at all levels of the management chain), but they tend to be the exception in my experience.
I've been at MSFT for 9 years and have yet to be issued a laptop. I've been MSFT for 9 years and have yet to actually need a laptop. :)
Indeed everything is dependent on need. PMs always get laptops because they spend lots of time outside of their office. On my team, most dev leads are also issued laptops. Friends of mine in teams closer to laptop features (think Windows 7 touch input, for example) never have had problems getting a laptop. On my current team, it's not common for an IC dev to have a laptop. It's also not common to find an IC dev with a machine more than 8 months old. I haven't quite figured out what everyone else's fascination is with laptops. I bought one for my own personal use, brought it to work, and then stopped bringing it because it just sat on my desk doing nothing 95% of the time. The other 5% I've replaced with post-it notes which, I'm happy to say, are available to both PM and Dev.