Can I or will I be able to run VSCode on Surface Pro X?

[vilicvane]

I use Remote SSH most of the time btw.

[FilipeRamalho]

This seems to be related to #33620
And there is already an x86 version of VSCode which should run on the Surface Pro X through x86 emulation.

[vilicvane]

@FilipeRamalho thanks for the reference. I am a little bit worried about the performance stuff. Can I rely on Surface Pro X to be my daily PC for development?

[FilipeRamalho]

@vilic Without going too much off topic. I am also considering the Pro X and thinking about the use of development tools on it. As it releases on November there is enough time to see if it's possible to use as an daily PC for development.
I can run VS Code on my SP4-m3, so it should work fine on the Pro X, but other tools like VS or IntelliJ may not work fine.
To quote Repo: Code on arm64

Personally speaking, the execution speed is damn fast (!). I tested on a Snapdragon 850 tablet w/ 8 Gigs of memory. The editing is quite smooth and the scrolling does not lag at all. The overall performance is better than a MacBook 12" (Core M/HD 615), even with several(9) extensions enabled.

[magic-k]

@vilic, @FilipeRamalho If you build vscode by yourself or get a arm64 version from a third party site you get code-oss. One of the major differences between official builds and open source builds is that the remote extensions refuse to work with oss. So in your case you will have to work in the x86 emulation. Which is probably currently the best way as the c# and c++ extensions also don't work on arm64. Probably a lot other extensions, too. Although i'm from the linux side i'm hoping that with the surface pro x native arm gets a bit of a boost.

[FilipeRamalho]

@magic-k I think that code-oss is a proof of concept, so we know that vs code itself can work on win-arm64.
It would be super cool if the linux community supports the Pro X to boost native ARM.
Don't the c# and c++ extensions work, because they are compiled to x86_64 or is there another reason?

[magic-k]

@FilipeRamalho I was more thinking the other way around. Microsoft forces it's own vscode department to support a native arm64 version, forcing the extensions to follow. From there a native linux version is probably only a short step. code-oss is the open source community portion of vscode, which works on all platforms you can compile it for including linux arm64 but without proprietary microsoft parts and native x86 parts.
Yes, these extensions contain native x86 components.

[FilipeRamalho]

@magic-k The VSCode community will hopefully follow and compile/support arm64.

[bvibber]

The primary trouble I have using the x86 VS Code build on an ARM64 Win10 laptop is that the remote extensions don't support ARM64 Linux (it seems to download x86-64 code which then fails to run?), so WSL-based development isn't as smooth as it could be.

Performance of the editor is adequate for my purposes.

[FilipeRamalho]

@Brion The extensions seem to be the primary problem when using VSCode are extensions with X64 code, I'm no that well-versed into Code extensions, but I will try to find out what is been compiled into x64 and if it can be compiled into x86 or even arm64.

[masknu]

I'm also thinking about using Pro X to develop Golang backend applications.

[magic-k]

As long as everything runs in the emulation, it'll probably works. delve, the golang debugger won't work on arm64.

[voronoipotato]

Firstly the original blocking issue has been resolved, there is official windows ARM64 electron support, hooray 🎉 .

I'm using a surface pro X now, the x86 version of code does work, but there's slightly disruptive visual lag on most actions, though typing seems to be fine. I'm also a mostly remote use person so I'm not dying here but it seems like it should be low hanging fruit.

[headmelted]

I'm happy to try adding this to https://github.com/headmelted/codebuilds now that Electron supports Windows ARM64.

Is there interest in this, given that it's not an official build so you would need to accept that there may be inconsistencies in terms of what's support from an extension perspective.