3 ms·
Depends on how you define "based on", I suppose. It comes from the same parent company, with a lot of interest in solving many of the same challenges. The UI
by horsawlarway 4y ago
Depends on how you define "based on", I suppose.
It comes from the same parent company, with a lot of interest in solving many of the same challenges. The UI paradigms are obviously related, and if you've ever done any real VS project debugging, you'll find the structure of those configuration files very (very) similar to how tasks work in VSCode.
I don't believe the VSCode codebase ever actually pulled anything from the original visual studio, but the roots of the application clearly come from the same place.
- pvg 4y agoIt's not meaningfully based on VS proper beside the name. The main difference is it lives in a very different ecological niche. Microsoft wouldn't have taken up its development if it didn't.
- 323 4y agoIf disruption does happen, it's better to be the one disrupting your own product than let others do it. Some people, a few for now, are migrating from VS proper to VS Code, including for languages like C++/C#. I am one of them.
- withinboredom 4y agoI can’t really use VS code for work (PHP support is nonexistent compared to PHPStorm), but I needed to make some changes to a C++ codebase in WSL. VS couldn’t get anything to work, I couldn’t even get it to compile. VS code got compiling and step debugging via gdb working after just a few tweaks to the make file and tasks. Worked like a charm.