Yeah, but the very nature of computer science tends to mean it's a turtles on down scenario. You explain that (for example), no, you can't upgrade the machine t

Yeah, but the very nature of computer science tends to mean it's a turtles on down scenario. You explain that (for example), no, you can't upgrade the machine to windows 7 from XP, and that's why your question is about XP, then you end up having to explain why you can't upgrade, which isn't just a simple reason. You go "well, because the framework we use only exists for XP" and now you're stuck explaining why you use that framework. Once you explain why you're using the framework, you're off to explain why you can only use that one framework and why nothing else will do. Then, you're explaining the problem that lead you to that framework, and on and on and on. It's typically never a simple "Well, we just chose X and that's why," it's almost always "We have to use x, because Y used N and M which don't work with L because J and we tried A, B, C, D and E, but only R worked, but R doesn't exist for the OS we use so we had to rewrite R in F and finally use it with X." You kinda end up copy pasting your life's story every time you ask a simple question. Drives me nuts and makes me use IRC more often because the feedback loop ends quicker.