Comment Re:Of course not.... (Score 1) 154
The IE guys are going to have to fix any problems in how it plays nice with Windows anyway, and if the development process is so broken that they can't even keep O/S-breaking regressions out of the builds, there's a problem.
The problem is that IE is tightly coupled with several other Windows components. This means it can break many other apps which can depend on it, or also can break itself if it depends on something which is not available.
For example, when IE7 came out people were extracting the installer package and installing the individual components inside to bypass the WGA check. If they didn't install the XMLLite component before the IE application installation, it would break several applications including Explorer. It could be fixed if the user booted to Safe Mode and installed the XMLLite package or DLL afterwards, but many users probably didn't know that.
This is exactly the kind of thing Microsoft wants to avoid...people breaking the system because they don't have the proper dependencies installed or some other factor with their configuration. It's much easier to roll it all together into a release canidate where they can be sure it includes everything it needs.