Microsoft has been recommending out-of-process extensions for quite a while now;
In other words, Microsoft has been recommending rearcheticting your extensions from the ground up, because their own code base is too messed up to support 64-bit.
And it looks like JetBrains is doing that, but it takes years for such massive codebase.
Rearchitecting the extension out of the process makes sense. You can easily trace performance issues to an extension and they don’t have to build a bunch of extension performance tooling in the ide
It's not just 32 vs. 64 bit. There are many other reasons that require separation. Stability, performance, different dependencies from the IDE process, ...
Comments
In other words, Microsoft has been recommending rearcheticting your extensions from the ground up, because their own code base is too messed up to support 64-bit.
And it looks like JetBrains is doing that, but it takes years for such massive codebase.
Visual studio is 64 bit now.
Rearchitecting the extension out of the process makes sense. You can easily trace performance issues to an extension and they don’t have to build a bunch of extension performance tooling in the ide
It's not just 32 vs. 64 bit. There are many other reasons that require separation. Stability, performance, different dependencies from the IDE process, ...