Live data from Hacker News

VS Code Roadmap 2018

github.com

141–150 of 236 posts

Re: VS Code Roadmap 2018

#141
post #80

Earlier quoted context omitted.

Not OP, but my browser is open pretty much all the time, and pinning tabs ensures they don't get lost.

So today I just learned you can pin tabs :)

I have GitHub, slack, Gmail, calendar and JIRA always pinned. That’s my most used web apps.

Can’t imagine them each having a desktop app. I would just get lost switching tabs.

Re: VS Code Roadmap 2018

#142
post #127

Is anyone aware of an article detailing how the VS Code team was able to realize so much performance out of Electron? VS Code is one of the most native-feeling, lightweight Electron products I've used (as compared to say, Slack) and I wonder how they got there.

Like any webapp they analyzed their paint times and made great performance improvements.

From the data structures of how they store lines and tokens of currently edited files, scrolling, refreshing changes on the screen etc they analyze perf, see what can be optimized and make it happen. Very few teams put perf above features at MS. Vscode is exceptional in that sense.

Also vscode uses processes quite a bit. The main app lives on one process, the language servers are all different processes, extensions are different processes etc. all communicating over jsonrpc

This means the main editor cannot get clogged by an extension hanging up or crashing.

Re: VS Code Roadmap 2018

#143
post #108

Has configuration become any better? I tried using VS Code for both Go and Python and all the magical stuff you needed to add to JSON files in weird places became a show stopper. I simply cannot figure out how it ties together and or figure out what my configuration options are.

I also found configuration to be obnoxious when I first tried VS Code. It's better now. It's still a JSON file, but the UI for editing it has improved a lot over the past year or so. You can search/filter the default configuration to see what options are available, and then you can just click each option to override it in your user or workspace config.

Their roadmap says they are working on settings ui improvements. I look forward to that.

Re: VS Code Roadmap 2018

#144

Earlier quoted context omitted.

YMMV I suppose, but I’ve never noticed the startup times, and I frequently create/close windows (I often have 2-3 at a time).

I just started visual studio code on my workstation, and it took 9 seconds to display a window, followed by 2 more seconds before populating it with an empty document. Sublime was sub second startup

I've always had sub second startup times. With text rendered within the first 1.5-2 at most. Time to "Actual interactivity" usually takes around 3-5 seconds, but that's mostly due to my plugins. I could start typing per-se, just not in Vim mode.

I mostly leave the editor permanently open on the project I'm working on, so I guess I don't really notice it much either way. And using the integrated terminal to change one dir back and switch to another project, then opening it with code . is a pretty good flow so I don't feel stifled in that sense either.

Re: VS Code Roadmap 2018

#145
post #67
post #47

Earlier quoted context omitted.

The regular Visual Studio uses about the same amount of memory as VSCode while being an order of magnitude more complex and feature-rich.

A small bit of anecdotal evidence: We have a solution with around 30 projects in it - this solution consumes around 1.25gb of RAM in Visual Studio. In contrast, the same solution in VS Code open along with two other windows open to other solutions are using a total less than around 300mb.

Yet I have 32 GB of RAM on my machine, and rather than use any of that, VS2017 will just use Its the main reason I'm excited about Rider.

Re: VS Code Roadmap 2018

#146

I use VS Code and enjoy it very much. However, for some reason the git diff visualizer doesn't really work anymore - I have to re-open the IDE to get it to show new changes to saved files. Anyone else have this issue?

> for some reason the git diff visualizer doesn't really work anymore

Yep, exact same issue with recent releases VS Code releases on RHEL. Every few days VS Code starts diffing against an old version of the code and I have to completely exit and restart.

Re: VS Code Roadmap 2018

#147

Earlier quoted context omitted.

> I’m not monogamous with my code editors I’ve always wondered why some people seem so married to a single editor. Based on the file type or context I might bounce between a number of them. I used to use Sublime Text a lot, but that’s been completely replaced for me by VSCode. I use IntelliJ IDEA predominantly for Java, Groovy, Python, Kotlin, PHP. I’m not a fan of its type hinting for JS or suggestions for HTML/SASS…

> I’ve always wondered why some people seem so married to a single editor. Familiarity, such as keyboard shortcuts. Especially for VI(M) or Emacs users, using anything else is an absolute nightmare. If you haven't been spoiled by VIM, then there really isn't much difference between "all those other editors". :wq

I started using Emacs like twelve years ago. At this point I'm hopelessly lost to it. My fingers natively speak a language that other editors don't understand.

Re: VS Code Roadmap 2018

#148
post #38
post #3

As much as I wanted to like and use VS Code, Electron base still ruined it for me. If it was some other app where I do not expect instant snappiness and lower memory usage, for example, Slack (also Electron app), I would swallow it, but for an editor, I can`t.

Well, the regular Visual Studio is a native app and has terrible performance and memory usage too. (joking but also serious)

I assume you use ReSharper? I have a 1M+ LOC C++ application that I work on regularly and have never had a performance issue. There was definitely slow down when I moved from VC6 to VS2005, but man, that was so long ago.

Re: VS Code Roadmap 2018

#149

Earlier quoted context omitted.

One very specific performance metric is startup time, and Sublime beats the pants off VSCode in that department. Creating new top-level windows in VSCode is also annoyingly slow compared to Sublime (presumably because it's spinning up a new browser context). Other than that, it seems snappy enough.

Sure, Sublime is practically instant whereas VSCode takes... maybe slightly more than half a second on my machine. It’s noticeable but is it really that much of an issue?

It's more noticeable on some peoples machines/setups, and some people are more sensitive to this type of performance.

Re: VS Code Roadmap 2018

#150
I tried VS Code for a while and the vim integration is really good. Unfortunately it's just not-quite-there IMO. I have a few muscle-memory things like ":tabe foo" that breaks when I try the tab completion (and IIRC it does something irritating like moving focus).
Post reply on HN