C'mon, you're a developer (presumably). You know we work in layers. 99% of the code will be platform-agnostic, and the entire thing would work fine if the platform-specific layer(s) underneath is (are) updated.
Most of VS is written in C#. And now .NET is crossplatform. WPF still isn't, but that could be fixed as well. If Qt can do it, so can M$ (I don't use this name in a negative way, but as an indicator that they have the financial resources to achieve it).
C++ is a native language, closely tied to architecture/memory/etc. .NET OTOH was designed to be a portable VM runtime. That's how they got .NET Core working crossplatform within less than a year, with only 10 people working on it. Suddenly hundreds of millions of .NET LOC can run on OSX and Linux.
Your application code is (should be) platform-agnostic. Especially for something high-level like an IDE, we're not talking about drivers here, look at how all of Jetbrains' Java-based IDEs are fully crossplatform. It's up to the layers beneath you to fix their platform-specific code to let your application work on other platforms. For Visual Studio, now that .NET Core (including filesystem, network, etc.) is crossplatform, the only thing left to port is the WPF layer.
Visual Studio is not only supporting .NET but also their C++ compiler.
.NET Core is FAR from the whole .NET framework. You have no support for winforms either nor things like Entity Framework (only the new rewritten version that is not released yet)
I know UI (WPF/WinForms) isn't multiplatform yet, I said so, but if Qt and Java-whatever can do it, so can MS. WPF is already an abstraction layer with very little Windows-specific code (ie taskbar, jumplists, which in Qt are optional Windows-only classes), they just need that abstraction layer to be implemented on other platforms. It would only be the outer-most layer that needs fixing.
3
u/cc81 Dec 05 '15
It would be a huge amount of work and up to now most of the things you produce with it would not even compile on other platforms.