This goes along the line of XHTML strict. A good move by MS in my opinion. Developers *should* be thinking about these things, not be lazy and depend on others to make sure they do things correct.

That's certainly one way of looking at it. However, when your company has been programming long enough, you'll find that maintaining old code becomes a big part of your job and there's no way around it. I don't *want* to have to spend 6 months rewriting 75,000 files (my guess as to about how many files are involved with all our websites) just to update to the latest version of Windows. If that's something you want to do all-day, every-day for no money (clients frown upon paying for that stuff) ... send me your resume.

You could say "you should have done it right the first time", and I'd have to say "yeah, you're probably right. And as soon as time travel is invented, I'll be the first one to go back in time, convince my company to hire me 6 years before I applied for the job, and tell all the developers to make sure to always use \r\n when sending emails."

Bottom line: backwards compatibility was sacrificed. I don't care why. I don't care how. I just care that my websites are fucked.

If you move your App from one platform (IIS5) to another (IIS6), you should NOT expect the same behavior, nuances, and so forth. Its just not possible and has produced the side effect of DLL HELL. As an industry we're all TRYING to move away from extreme backward compatibility (Microsoft being the BIGGEST antagonist on this front: imagine backward supporting RESERVED STRUCTURES because some arcane program USED THEM?!)

Oh, and when you get to Seoul, hook me up with a cute Asian girl too ;-)

<i>Oh, and when you get to Seoul, hook me up with a cute Asian girl too</i>

Sure, if you speak Korean this will be no problem.