3 ms·
I wouldn't be surprised to see VS Code replacing VS entirely. Visual Studio is built on WPF and it's probably as massive of an effort to port all that over as
by rblatz 8y ago
I wouldn't be surprised to see VS Code replacing VS entirely. Visual Studio is built on WPF and it's probably as massive of an effort to port all that over as it is to bring Code up to snuff.
- pjmlp 8y agoThe Electron pleasure. I tremble to imagine how many cores and GBs would be needed to have VSCode with the same capabilities of Visual Studio Ultimate, while running at comparable performance.
- nicoburns 8y agoVSCode has performance sensitive bits (such as file search) written in Rust and (I believe) C++, so it's not out of the question...
- pjmlp 8y agoI am forced to use it in a couple of projects and fast it is not. Specially when comparing with the likes of Sublime, which I gladly payed for.
- thrower123 8y agoWill never, ever happen. Electron is not feasible, and moreover, the VS team is not going to rewrite all their funcionality, when they can't even give us a 64 bit VS.
- untog 8y ago> when they can't even give us a 64 bit VS Wouldn't that encourage a switch to a totally new system? If you have to do a ton of ground-up work to get VS working 64 bit, you could argue you as well expend the same effort in getting VS Code to a level where it can be used instead of VS.
- thrower123 8y agoI dunno, people have been hoping for a 64-bit VS for like a decade. The excuses have been unconvincing.
- jenscow 8y agoWhat are the reasons for wanting 64-bit?
- scarface74 8y agoMicrosoft's semi-official stance on why VS isn't 64 bit... https://blogs.msdn.microsoft.com/ricom/2015/12/29/revisiting-64-bit-ness-in-visual-studio-and-elsewhere/ https://blogs.msdn.microsoft.com/ricom/2015/12/29/revisiting...
- thrower123 8y agoI thought this was crap three years ago, and I think it is worse now.
- wglb 8y agoBecause?
- manigandham 8y agoBecause solutions and IDE functionality is getting more complex and processes needs access to more RAM, which is cheap and plentiful and pointless to not use. Saying that every extension should be its own process isn't sufficient and ignores the extra complexity, inefficiency and resources that approach takes. What's worse is that VS doesn't even follow its own recommendations. Even with the massive upgrades over the past year, it's still extremely slow and laggy on any sizable solution.
- pjmlp 8y agoActually being its own process it is something I came to agree upon. In process plugins look cool, but they just bring everything down when they misbehave, plus it is another opportunity for exploits. Peformance can be improved by actually writing the plugins in languages that compile to native code and eventually use shared memory. Now if one uses node for everything naturally it doesn't scale.