News for hackers. Stuff that matters.
Re:Insider Build of VSCode for Windows/ARM64 by ebg13 on Friday May 29, 2020 @09:53AM (#23349970)
> VSCode is using about 300MB+ and Sublime Text (working under built-in ia32 emulation) is using 15MB.

On my mac VSCode sits at ~380MB without any files open, but opening one empty plaintext file brings that up to 460MB, opening one tiny Lua (a language known for being especially small and efficient) file makes that 500MB, and opening a second tiny Lua file makes that 535MB. Does Sublime increase like that?

Re:Insider Build of VSCode for Windows/ARM64 by revnode on Friday May 29, 2020 @10:13AM (#23350166)
There are advantages to having VSCode in Electron. I run VSCode as a web application on my server that I access remotely using a browser on a number of different machines. That instance has access to the file system on my server, allowing me to use any machine to do my work without installing anything. Try doing that with Sublime.

Microsoft is leveraging this by allowing you to open up VSCode in Github for any file, no installation necessary. Amazon is doing the same with Cloud9 on AWS that they acquired earlier.

Re:Insider Build of VSCode for Windows/ARM64 by benologist on Friday May 29, 2020 @10:18AM (#23350227)
You don't actually need to install VSCode on the server - the SSH extension lets you use VSCode locally.

https://code.visualstudio.com/docs/remote/ssh

Re:Insider Build of VSCode for Windows/ARM64 by w0utert on Friday May 29, 2020 @11:43AM (#23351332)
That's useful, but I think the person you were replying to doesn't just use the host machine as a remote file system but also as a build host and to have a single workspace with all its settings available from any machine.

I recently set this up as well using code-server [1], which works brilliantly. I have a VM running on a powerful hypervisor host, which has all the source code, the workspace configuration with all my customisations, build tasks, etc. Compilation is fully on the host side, which is a 12-core with 32GB memory, way beyond any of the computers I use as clients, and all I need to access it is an SSH connection to it. Code-server has a progressive web app mode that makes it pretty much indistinguishable from running a local installation. First time I have had to acknowledge it wasn't such a bad idea to implement VSCode as an Electron app to be honest.

[1] https://github.com/cdr/code-server

Re:Insider Build of VSCode for Windows/ARM64 by AaronFriel on Friday May 29, 2020 @01:56PM (#23353259)
The ssh extension actually does all of that as well, but it does mean the frontend runs in the Electron app vs in a browser. The first thing the ssh extension does is install the VS Code server backend in the remote host, enabling the remote host to run extensions, the terminal, and so on.
Re:Insider Build of VSCode for Windows/ARM64 by danieldk on Friday May 29, 2020 @11:38AM (#23351238)
That instance has access to the file system on my server, allowing me to use any machine to do my work without installing anything.

Many editors have had remote editing support for a while. It requires that you have installed the editor locally, but why wouldn't I have an editor on my laptop or desktop?

(Tramp + LSP all the way ;).)

Though being able to open VS Code in GitHub is a really nice feature!

Re:Insider Build of VSCode for Windows/ARM64 by revnode on Friday May 29, 2020 @12:03PM (#23351630)
> why wouldn't I have an editor on my laptop or desktop

Because it's not just the editor. It's the toolchain. I get remote terminal inside the editor. All my tooling lives on the server and can be specific to the project I'm working on, instead of gumming up my local machine.

Re:Insider Build of VSCode for Windows/ARM64 by danieldk on Friday May 29, 2020 @02:22PM (#23353623)
If you use e.g. the Emacs LSP package and edit files remotely through Tramp, you are using the remote toolchain, language server, etc. [1]

(Though for me it doesn't really matter, because I can reproduce exactly the same environments between server and local with Nix.)

[1] https://emacs-lsp.github.io/lsp-mode/page/remote/

Re:Insider Build of VSCode for Windows/ARM64 by zenlot on Friday May 29, 2020 @02:02PM (#23353369)
Have you heard about Emacs? It has all the features and more. Plus had them for long long time. 44 years on.
Re:Insider Build of VSCode for Windows/ARM64 by revnode on Friday May 29, 2020 @04:40PM (#23355242)
Indeed I have. I just don't want to party like it's 1976.
Re:Insider Build of VSCode for Windows/ARM64 by danieldk on Saturday May 30, 2020 @02:04AM (#23358892)
Yet, you are probably deploying on an operating system that is a clone of another operating system that was started in the early 70ies.
Re:Insider Build of VSCode for Windows/ARM64 by revnode on Saturday May 30, 2020 @11:26AM (#23361791)
Just because I sometimes go through a tunnel doesn't mean I want to live in a cave.
Re:Insider Build of VSCode for Windows/ARM64 by eronhp on Friday May 29, 2020 @01:24PM (#23352799)
Your setup sounds really intersting, do you have any links for tutorials on how to setup something similar?
Re:Insider Build of VSCode for Windows/ARM64 by AaronFriel on Friday May 29, 2020 @01:55PM (#23353241)
Not sure if the parent poster has a custom setup, but there's now tooling to set this up yourself and use Microsoft as a secure proxy so you can access your host from anywhere in the world: https://docs.microsoft.com/en-us/visualstudio/online/referen...

You can also "cheat" and instead of registering your VS Code server instance with Microsoft and find the path in your ~/.vscode-server or whatever directory, and there should be a shell script that starts it and runs VS Code on port 8000. You can then set up any reverse proxy/TLS/auth layer in front of that and access it similarly.

I think the VS Online (now called VS Codespaces) experience is a bit better but the process of creating an account and logging in is messier.

Re:Insider Build of VSCode for Windows/ARM64 by revnode on Friday May 29, 2020 @02:01PM (#23353343)
Re:Insider Build of VSCode for Windows/ARM64 by soapdog on Friday May 29, 2020 @10:34AM (#23350367)
It doesn't grow like that in my experience.

I just loaded the source for Luarocks on Sublime Text and my RAM usage while browsing some Lua code in it is 31MB, pretty decent.

If you're doing Lua, there is always Zero Brane Studio (https://studio.zerobrane.com/) which is built with Lua and very nimble (uses wxLua which is wxWidgets + Lua), unfortunately it is not playing well with my hidpi screen. Another good option for Lua developers is TextAdept (https://foicica.com/textadept/) which has wonderful support for extending it using Lua, IMO it is like an Emacs but with Lua. Those editors are available as ia32. I didn't succeeded in compiling ZeroBrane studio for arm64 even though I managed to compile both Lua and wxWidgets for it. As for TextAdept it uses GTK and that is not available for Windows on ARM.

For the past week I've been using sublime text and am quite happy with it. I also use VSCode when I need some more intelisense help.

Re:Insider Build of VSCode for Windows/ARM64 by wbond on Friday May 29, 2020 @10:10AM (#23350127)
Ram usage will increase in Sublime Text as syntaxes are loaded into memory. The last time I checked on a Mac, loading every single default syntax would get you in the low 200MB range.

A large part of that with the current stable builds is syntaxes that embed others - so Markdown fenced code blocks and LaTeX files. For simpler syntaxes you’ll see a much smaller jump in ram usage.

Re:Insider Build of VSCode for Windows/ARM64 by tester89 on Friday May 29, 2020 @01:00PM (#23352475)
No. Once I reached 750 MB but that was because I was working on a JS project with a `node_modules` of 110 MB and by default ST indexes the text contents of all files so I can do find all across files. After that folder was excluded, it took 250 MB and it was indexing 20 MB.

See also: https://github.com/jhallen/joes-sandbox/blob/master/editor-p...