3 ms·
I'm not sure what your definition of an IDE is, but the notion of a core platform with language-specific extensions on top long predates VSCode. Visual Studio p
by int_19h 6y ago
I'm not sure what your definition of an IDE is, but the notion of a core platform with language-specific extensions on top long predates VSCode. Visual Studio proper works in exactly the same way, for one; and then there's Eclipse, NetBeans etc. If anything, this has been the conventional way to do IDEs since early 00s or so.
- pjmlp 6y agoEven earlier, Turbo Pascal 6 came with the Turbo Vision framework which was used to create the IDE as well. Studying how the IDE made use of Turbo Vision was a good introduction to OOP ideas.
- jolux 6y agoWith Code they’re running out of process and communicating via IPC/RPC most of the time which introduces instability that I’ve never experienced in Visual Studio, Rider, or IntelliJ
- int_19h 6y agoThere are many things in Visual Studio that run out-of-process, and coordinate via IPC. It's an implementation detail, and does not change the fundamental approach. Also, many things in VSCode can be done in-proc as well if one so desires, including debuggers and language servers. Most extensions do them out-of-proc because it gives them more flexibility (esp. wrt implementation language for those components), and because it's easier to test such isolated components.
- jolux 6y agoYeah, and I hate Visual Studio for the most part too. It's a bloated mess. JetBrains' .NET IDE Rider is much better.