At Mobile World Congress, a Microsoft executive said that in the next release of Windows 10 to Insiders, Spartan would be part of the build. But with today's release of 10041, Spartan is not part of the package. We got a chance to chat with Gabe Aul, ahead of today's announcement, about why Spartan is absent.
Firstly, as Aul has stated before, saying exactly when features will ship is hard to pinpoint and at this time, Spartan is not ready. He stated that Spartan is still being tested internally and that the team "has to complete a few more tasks before it is ready to ship".
While we know this is not what Insiders want to hear - as many were hoping to play with the new browser- in this iteration, Microsoft has a defined process for when features are ready to be flighted to Insiders. Also, you have to consider the impact of releasing a buggy version of Spartan.
Spartan is much more than a new browser for Microsoft; it is a fresh start for their fight to maintain market share lead in the browser segment. If they release a buggy build of Spartan, there is a possibility that the browser will immediately be burdened by negative perceptions before it even hits market - andMicrosoft cannot afford for this to happen.
So for now, we have to wait a bit longer as Microsoft refines Spartan, but if you do want to try out the new rendering engine, here is how to enable it in build 10041.