Hey folks, don't forget that these guys still do this:
VSCode January 2019 (version 1.31) released
31–40 of 41 posts
Re: VSCode January 2019 (version 1.31) released
#32Hey folks, don't forget that these guys still do this: https://github.com/dotnet/cli/issues/3093 https://github.com/dotnet/cli/issues/10497
???
The article is for microsoft/vscode.
Your links are for dotnet/cli.
Re: VSCode January 2019 (version 1.31) released
#33I tried VS Code early on and decided I'd give it a serious shot when I could modify the color scheme without having to go through a whole page of notes, download and install something like 3 other programs and practically learn a whole new language. Is that possible yet? In other words, is there an actual GUI for configuring color, or at least a config file that's not some cryptic format for a program I've never used…
Yes - https://code.visualstudio.com/docs/getstarted/themes
(I also recall the process being rather user-unfriendly in earlier versions)
Re: VSCode January 2019 (version 1.31) released
#34Hey folks, don't forget that these guys still do this: https://github.com/dotnet/cli/issues/3093 https://github.com/dotnet/cli/issues/10497
??? The article is for microsoft/vscode. Your links are for dotnet/cli.
It's Microsoft telemetry in an open source project that doesn't respect the setting set by the user. The lack of a reply as to why should probably set off some alarms for the average tech user when it comes to any project with Microsoft telemetry in it.
Re: VSCode January 2019 (version 1.31) released
#35This allows you to create a VS Code terminal panel, which occupies the complete editor area as shown below: Emphasis on: which occupies the complete editor area as shown below: So finally windows has a decent terminal emulator, will install vscode just for this next time I'm on windows.
It's using xterm.js which has limitations on windows, for example PowerShell/cmd.exe will report mouse movement and I have not been able to get xterm.js based terminal emulators (vs code, hyper) to do the same.
Re: VSCode January 2019 (version 1.31) released
#36Did you guys noticed the Marie Kondo reference?
I also saw a sneaky reference to Brazil (the film)
Re: VSCode January 2019 (version 1.31) released
#37At this point I am 100% sure, VS code will become a IDE like Visual Studio.
I thing it's already more an IDE than a plain editor. There is not even a normal file-explorer anymore, just an workspace-explorer. Using VS Code for regular editor-stuff is kinda painful IMHO.
Re: VSCode January 2019 (version 1.31) released
#38Did you guys noticed the Marie Kondo reference?
She keeps popping up: https://twitter.com/iamdevloper/status/1090617583433404416
Re: VSCode January 2019 (version 1.31) released
#39Vscode is great, but it's a pitty they are running it on electron. 1.3GB of RAM usage for a 8GB machine is not efficient at all.
I switched to sublime3 because of this, sublime is great, really fast, only uses 300mb of RAM, unfortunately the packages and plugins aren't as streamlined as vscode. Hoping they improve this.
Re: VSCode January 2019 (version 1.31) released
#40Vscode is great, but it's a pitty they are running it on electron. 1.3GB of RAM usage for a 8GB machine is not efficient at all. I switched to sublime3 because of this, sublime is great, really fast, only uses 300mb of RAM, unfortunately the packages and plugins aren't as streamlined as vscode. Hoping they improve this.
I think this is only a problem when working unplugged. I have visual studio code sitting idle all the time and it really doesn't seem to slow down my system. It generally only uses about 500MB of RAM with two windows open with multiple tabs on each. I have 16GB of RAM but thats not much compared to today's standards.
Sublime text using 300mb of RAM is a little odd. Generally in my case, its uses around 20-25MB with 50+ tabs opened.