Microsoft Declines To Make a 64-Bit Visual Studio (uservoice.com)

OhPlz writes: A request was made back in 2011 for Microsoft to provide a 64 bit version of Visual Studio to address out-of-memory issues. After sitting on the request for all that time, Microsoft is now declining it, stating that it would not be good for performance.
After almost five years, the request received 3,127 votes on the UserVoice forum for Visual Studio. Microsoft instead recommended the vsFunnel extension to optimize memory by filtering low-priority projects, adding "we highly value your feedback." They cited a December MSDN post that had argued "smaller is faster," and that no performance benefits would be realized for users whose code and data already fit into a 32-bit address space, while most other issues could be addressed with better data design.

Comments

Re:In other words...

[DaHat]

I have a solution with a half dozen projects that can hit the memory wall in a couple days or so.

I find that when I drive my car for extended periods that things no longer work as well as they used to. I'm told I should check my fluids from time to time but never bother to get around to trying to figure out why pert goes down over time.

Perhaps it's that the IDE leaks memory badly, in which case 64-bit would let it leak worse.

Perhaps it's that OhPlz drowns kittens to get off.

Either way though, it needs to be addressed.

Agreed, we should do something about your hypothetical drowning of kittens.

Their response was completely lame

So you've actually read the MSDN article referenced in the story above? The reasons described are not unreasonable, and pretty well known who care about perf optimization.

They've done great things with C# and C++ lately which means they're putting money into the product, it's bizarre that they're passing on this

One thing does not follow from the other. C# & C++ are languages that work quite well from Visual Studio *AND* the command line. Visual Studio is simply the shell which loads oodles of MS built plugins to show the code. Improvements in the language do not automatically mean new VS tooling.

I'd take it even if some features were missing and were added back in as updates later on.

You seem to be in the minority on this, as while 3100 votes (not people) sounds like a lot, it's a drop in the bucket compared to the # of people who use Visual Studio.

Re:In other words...

[Fragnet]

I've been using Visual Studio for 15 years and have never had that problem. Perhaps you're doing something dumb.