64bit version for Windows?

[Stanzilla]

Is there a reason why there is no 64bit version of Code for Windows? I get that Electron 64bit was only released after Code was already out but is that the only reason? :)

[joaomoreno]

Really is... Need to fix!

[Stanzilla]

Is this still on deck for 1.0 or later?

[joaomoreno]

Not forgotten about, just not for 1.0.

[jrappen]

Any updates?

---

References for Electron:

• issue: Windows 64bit release electron/electron#980
• pull request fixing that issue: Add 64bit Windows build electron/electron#1405

[Stanzilla]

VS Code might have the same problem as Atom that all the extensions will have to be recompiled if the user migrates from 32bit to 64bit so that might actually be non-trivial to do.

[ghost]

Updates?

[joaomoreno]

No updates here yet. But it will come.

[jrappen]

Please also consider adding a portable 64bit version (compare #329).

[josemi-ca]

Any update on this?

[jrappen]

@joaomoreno compare atom/atom#13135

[iam3yal]

@joaomoreno Any updates on that?

[MikeGitb]

Why was the 32 bit version the default in the first place? Why not directly develop for x64?
Seriously: What is Microsoft's problem with x64? Just from the top of my head:

• VS isn't x64
• they still recommend to install the 32 bit Version of Office
• The default project type in VS is still 32 bit
• vcpkg (c++ packet manager) install 32bit libs by default - even on a 64Bit system

Does your telemetry show that there is actually a sizable user base that works on a 32 bit version of Windows? I can understand that it might not be trivial to port a mammoth like the actual Visual Studio, but here you more or less started from scratch and didn't have to pay any attention to backwards compatibility.

Sorry for the rant, but this is bugging me every time I use/install MS products for devolpemnt ... In general I'm very happy with VS-Code

[be5invis]

@MikeGitb
I think some C++ extension are blocking them.

[wizarrc]

@MikeGitb 32-bit office is recommended for macros (VBA) back compat. VS is 32-bit for the longest time because they found ways to make everything out of proc, and 64-bit tends to have a lot of code size bloat when references other objects using 64-bit pointers instead of 32-bit. That also helps make code run faster even in a 64-bit OS. I'm not sure exactly how much of a perf hit you take, but for perf sensitive apps like VS, that was a top concern years ago.

[benyaminl]

But atom has 64 bit and it's normal though.

On Fri, 26 May 2017 at 06:58 Thomas J. Crowe ***@***.***> wrote: @MikeGitb <https://github.com/mikegitb> 32-bit office is recommended for macros (VBA) back compat. VS is 32-bit for the longest time because they found ways to make everything out of proc, and 64-bit tends to have a lot of code size bloat when references other objects using 64-bit pointers instead of 32-bit. That also helps make code run faster even in a 64-bit OS. I'm not sure exactly how much of a perf hit you take, but for perf sensitive apps like VS, that was a top concern years ago. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#507 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACr9NC-KVqqtaOCRw6Vn_V_RmjoO4R-vks5r9hWUgaJpZM4Gnsk-> .

-- Benyamin Limanto sent from Inbox for Gmail

[MikeGitb]

@wizarrc: I've heard the perf argument a couple of times now and I frankly don't buy it. I have yet to see a single program whose x64 Version is noticeably (not just measurable) slower than the 32 bit version. Also, I'd certainly prefer a slight drop in performance to the occational out-of-memory errors on larger projects.

In the End, I didn't want to argue about the individual reasons for or agains a x64 version, Just that I see a general - and very disapointing - pattern where MS and 64Bit software is concerned. Almost as bad as the general lack of utf-8 support (which is admittedly a result of Microsoft early embracing unicode in the first place).

[wizarrc]

@MikeGitb I agree. Nothing is more annoying than hitting a memory limitation when your dev machine is loaded with RAM. I've seen some blog rants about why to use 32-bit. I was just answering your question from my perspective of what I have seen as the attitude toward 64-bit years back as to what their problem is. I think it was mostly based on sub-optimal design which had a lot of performance bottlenecks beforehand. A way back then to hit their perf metrics was to not upgrade to 64-bit. Remember, a lot of that was legacy code moving forward, and 64-bit requires a lot more localized programming techniques (less 64-bit pointers) to keep bloat down. As for newer code bases, it should be easier to tackle.

[joaomoreno]

The infrastructure work for this has been done. 64 bits will come out with June's release for Insiders and with July's release for Stable.

[saschanaz]

It's not exposed on the webpage but the link is here: https://code.visualstudio.com/docs/?dv=win64, which currently gives VSCodeSetup-x64-1.14.1.exe.

[oplexz]

It's not exposed on the webpage but the link is here: https://code.visualstudio.com/docs/?dv=win64, which currently gives VSCodeSetup-x64-1.14.1.exe.

Thanks

[jrappen]

@saschanaz That is the installer version, not the portable.

@joaomoreno Is there a 64-bit portable release available?

[pltrant]

Zip version: https://code.visualstudio.com/docs/?dv=win64zip&build=insiders

[jrappen]

Thanks, @pltrant. It also works without the build=insidersquery-string part, although there are still some issues remaining (see #329) with the portable 64bit version.

[WildByDesign]

Stable 1.14.1 now provides download links for 64-bit installer and zip.
Link: https://code.visualstudio.com/#windows64-download-stable

[kuechlerm]

@WildByDesign That link ist broken.

Use: https://code.visualstudio.com/updates/v1_15#_windows-64-bit

[benyaminl]

Just open the vs code download page, select other version, and select the 64bit version. The new version arrived today. Benyamin Limanto sent from my ASUS FonePad 8 Pada tanggal 16 Agt 2017 14.23, "kuechlerm" <notifications@github.com> menulis:

…

@WildByDesign <https://github.com/wildbydesign> That link ist broken. Use: https://code.visualstudio.com/updates/v1_15#_windows-64-bit — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#507 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACr9NJ-LGLlZaUZouxjB19J-WTmIvyNmks5sYpkDgaJpZM4Gnsk-> .

[roachsinai]

@MikeGitb I saw a same question on Zhihu website. The same guy？

[MikeGitb]

@roachsinai: If you are asking, if I'm the same guy that posted something on Zhihu, then the answer is NO, as I didn't even know the site up until now.

[roachsinai]

@MikeGitb OK. I see.

[MikeGitb]

Did the person ask the exact same question or just about getting a 64bit Version of msvc? Because the latter is actually very common.

[eromoe]

Should we replace 32bit to 64bit ? what is benefit and disadvantage ?