I don't think they need to embed a browser into VSCode considering it's already running in one (Electron). However I wouldn't be surprised to see a browser embedded into a browser these days either.
I'm pretty sure the electron browser engine moves slower than Blink.
If so, it would be extremely unhelpful for development and debugging since you would rarely have the latest engine on your machine, which would be the engine the majority of your customers would be on.
Using an external browser makes a lot of sense in that regards, and also, it separates the testing engine from the application itself, which allows for (although I doubt it's been implemented yet) testing in different browsers, or different versions of browsers, etc.
> I'm pretty sure the electron browser engine moves slower than Blink.
> If so, it would be extremely unhelpful for development and debugging since you would rarely have the latest engine on your machine, which would be the engine the majority of your customers would be on.
I would think that it would make sense to A) test in a slower browser anyways -- if your code runs well in a slow environment it'll run in a fast one as well, and B) Test in multiple browser engines anyways. Why would you only test one engine?
It makes logical sense that MS would start with Edge, but I can see (for standards compliance) them expanding to work with other browsers too; it would be too great a selling point not to use.
