User:Gimmethegepgun/The Creation of Vista
Ah, Windows XP. Compared to earlier released Windows came out with (95, 98, and later ME, all from the same team) it is an AWESOME system. Compared to other computers on the market, it's actually good. Vista, however, is not. And yet, Vista is based off of XP. How did Microsuck screw it up so badly? Here's what I think:
- Take XP, a pretty good system as stated before, and put it on the table.
- Next, put the competing computers on another table next to it.
- Take apart the other computers and just put the good parts of them on the table, and throw the rest out.
- Then, melt down the good parts and form them into bullets.
- Use the bullets in the machine-gun laying on a third table, and just spray at complete random at XP.
Congratulations! You now have Vista! A massive conglomeration of the good parts of other systems, though without all the necessary parts to implement them properly, thrown at random at XP, destroying numerous portions of XP that work properly in the process, and leaving massive holes in the side (that Microsuck won't even cover up with some duct tape) for viruses to get in.
Disclaimer: It's not my fault if you took this literally and mowed down your XP computer in order to get a cheaper version of Vista.
Cute. However, in actuality, what you do is hire marketdroids who have no grasp of computers at all and make them Chief Designer and Project Supervisor. The rest occurs naturally as various programmer biases (and yes, we all have them) get sold to the idiot marketdroids as necessary and desirable, and, not having any knowledge of, or experience with, programming computers, said idiot has no way of telling who is BSing him and/or who is unable to get their head out of their rectum long enough to do a really good job of design. This, unlike the above, is NOT a facetious description. I know someone who met the project supervisor for VB when it was initially developed back in the early 1990s. Said idiot had no idea what a BNF grammar was, and, if you don't know that you clearly have no business being project supervisor of a major language update. It's something anyone completing their junior year working towards a BS in software programming should be at least functionally cognizant about. Not claiming you should not understand marketing at all, but if you don't know computers at all you cannot possibly tell when you are making good decisions from a software point of view.
