I work in the VS Code team - the experience you are having is not the experience we aspire to. It would be great to dig into this a little more and see what we can learn.
Perhaps the easiest way to have a deeper dialogue is via a GitHub issue. The easiest path to creating one is leveraging 'help->report issue' that will include some additional context that will help us dig in a little more.
Thanks, I’ve definitely not given up on VS code considering how soon after I started using it I already liked it as much as I do. So if I somehow manage to isolate/reproduce some of the problems I’m seeing, I will file an issue fo it.
As I point out in a sibling comment, reporting aberrant behaviour can be difficult because the cause is usually unclear. Why is Code Helper using 100% CPU? Who knows. It happens every few days and doesn't seem be related to anything specific I do. More tools (such as a "task manager" similar to Chrome's) to gain visibility into what VSCode is doing would help here.
For excessive Code Helper CPU usage, you should be able to surface what the file/arguments were used to launch a Code Helper instance (how you do this depends on the OS). That will tell exactly which component is acting up, eg. TypeScript, search, terminal, extension, etc.
This may be a recent change? The last time I tried reporting excessive CPU usage, the Code Helper process didn't have any context info in the command line.
We do have a plan to enable this - unfortunately it did not make 1.8 but we plan to work on it in 1.9. So you should have some additional options soon.
Is it possible to add for a way for the user to have a custom CSS file? I really like how Atom provides such great visual customization by just giving the user a less file that they can edit.
I love VS Code (we're pretty invested in TypeScript, so it was a natural fit), but the one thing I really miss from Sublime is that code preview thing that shows a bird's-eye view of the current file and lets you click around to any part of it. Any idea if there is or will be a way to enable the same functionality in VS Code?
Edit: Apparently this is called the "minimap" and is a popular feature request, so guess that answers that.
This was an oversight by me in a recent update - however -I've resolved it and with any luck made the statement even more visible for the users/anyone who does an update.
I work in the VS Code team - the experience you are having is not the experience we aspire to. It would be great to dig into this a little more and see what we can learn.
Perhaps the easiest way to have a deeper dialogue is via a GitHub issue. The easiest path to creating one is leveraging 'help->report issue' that will include some additional context that will help us dig in a little more.