3 ms·
That assumes that it is possible to strip down Visual Studio without refactoring to an extent that disturbs the development of the main product and causes more
by vertex-four 10y ago
That assumes that it is possible to strip down Visual Studio without refactoring to an extent that disturbs the development of the main product and causes more work than just developing VS Code from scratch - and that Visual Studio is portable to other platforms.
- mercer 10y agoI'm not sure if this came from the TypeScript team or if it was just a HN commenter, but I remember reading (a theory) that VSCode is, at least to a degree, meant to eventually become a clean rewrite for Visual Studio, or at least reach some degree of feature parity, and that this is why so much energy is put into this (which strikes me as noteworthy, the amount of energy that is). I'm not experienced with projects as large as this, but I could see how the work they're doing on VSCode would be worthwhile even if they eventually swap the web-based parts with more performant approaches (as the project expands to 'become' VS).
- tracker1 10y agoVS Code also had a huge headstart in that they already had the editor code, as well as the node+chrome workspace (electron/atomshell) to use. Not to mention cross-platform from the start. At this point, they actually have a lot of the core functionality in place for a full IDE, they just need a prettier means of editing configuration, and creating build-able projects.... It's a bit manual at this point, which makes it a good fit for node and go workflows, and decent for others. It will get better.