@P. Lee Re: "No wonder tech is hard" Whilst I agree that aspects of this article.........
........lack a certain clarity and the subheading is particularly unfortunate there is as yet no reason to assume that Redmond are going down that route again (indeed they would be very foolish to do so for a whole list of reasons). From the article:
"But he added that the build* also causes problems with Visual Studio 2015, the preview version of Microsoft's integrated development environment, and that coders who are using VS2015 to build Windows Universal Apps should probably stick to the older Build 10041 for now."
It becomes even clearer that that is not what is being said if one takes the opportunity to read the blog post by Gabe Aul cited in the article. Aul is referring to the build itself and not the browser. The trialling of Spartan for the first time is the big news but the build itself also causes certain problems which the Win 10 development team are working on.
Whilst I do not put it past MS to repeat previous foolishness we do not as yet have reason to believe that they actually are integrating the browser into the OS in the way they did with IE.