Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Integrated Terminal Performance Improvements

code.visualstudio.com

Post reply on HN
Print view View original

21–30 of 74 posts

Re: Integrated Terminal Performance Improvements

#21

Post by seanmcb »

w0utert wrote: post #11

I really wish Microsoft had used a different platform to build VS code on, like C#/Mono, Java, anything except Javascript/Electron basically. I just started using VS code for C++ development, trying to switch from Vim, an I basically like everything about the concept, but the execution and quality/polish of the software is mediocre at best. At least three times a day random stuff breaks: code completion stops working…

Hi @w0utert

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.

Re: Integrated Terminal Performance Improvements

#22

Post by w0utert »

CJefferson wrote: post #12
w0utert wrote: post #11

I really wish Microsoft had used a different platform to build VS code on, like C#/Mono, Java, anything except Javascript/Electron basically. I just started using VS code for C++ development, trying to switch from Vim, an I basically like everything about the concept, but the execution and quality/polish of the software is mediocre at best. At least three times a day random stuff breaks: code completion stops working…

Something is seriously wrong with your setup. I know many vscode users, and none of them are having your problems. I'm not saying you aren't having real problems, but they aren't common and they can appear in any editor -- I used to fill vim with plugins and it would hang frequently.

My setup is just the official, latest release, with the Microsoft plugin for C++, the Vim bindings everyone uses, and one additional plugin for switching between header and source. I customized nothing besides a few keybindings and enabling neovim mode. This is on Ubuntu by the way.

I also used VS code a little on macOS for web development, and to be fair, I didn’t run into any of these problems there. But that’s for projects that are literally 100 times smaller than the C++ project I’m working on.

I don’t really buy the anecdotal ‘other developers never have any problems with VS code’ observation. I’ve been following the VS code release announcements here on HN for a while (it’s what got me interested in trying VS code), and they regularly seem to contain fixes for weird platform problems or regressions, to the point they’ve even had to retract a few of them because of serious problems found after deploying the update.

Re: Integrated Terminal Performance Improvements

#23

Post by koolba »

> Misaligned characters: Due to many monospace fonts not being strictly monospace for some Unicode characters, this could lead to situations like the one seen on the right-side of the image below: (image)

What are they referring to? I've been staring at the pic for nearly a minute and can't see anything misaligned.

Re: Integrated Terminal Performance Improvements

#24

Post by Waterluvian »

FBISurveillance wrote: post #2

Obligatory comment: I really like VSCode but keep jumping back and forth between it and Sublime because of startup time. I like VSCode enough to use it daily and extensively and jump back to sublime when I need to jump around projects fast–when startup time becomes crucial. I believe they will solve this issue at some point.

By startup do you mean the initial loading of VSCode or the cost of switching project contexts within VSCode?

I wonder if you can just pre-load Code and hide it in some manner plus use CLI commands to open new folders/files within the existing VSCode instance rather than a new one?

I do agree, though. VSCode has so many benefits but every so often I hit an irregular usage where I'm opening lots of various stuff and its a bit slow.

Re: Integrated Terminal Performance Improvements

#25

Post by nwrk »

Waterluvian wrote: post #19

What's the case for using the terminal in VSCode? I use a modern multitasking computer where VSCode is in one area or screen and my terminal in another (and other things in others). By using my own terminal I get to keep everything custom about that terminal rather than having another one. Surely there's reasons that I'm missing? Edit: thanks for all the responses. A lot of great new things I didn't think of before!

For example, you can use linter in terminal which makes click on output messages interactive -> going directly to source code.

edit: quick youtube example how it works together https://www.youtube.com/watch?v=cMrDePs86Uo

Re: Integrated Terminal Performance Improvements

#27

Post by simlevesque »

polskibus wrote: post #9

That's great! Does anyone know if the code editor itself uses canvas rendering? If not then why?

The other comment is wrong.

I opened the DevTools inside vscode and executed 'document.getElementsByTagName("canvas")'.

In a single editor group[1] in edit mode there are two canvases. One is for the overview over the scroll bar. The second is the minimap. When you are in diff mode there are two more canvases to show the diff on the right side.

[1] https://code.visualstudio.com/docs/getstarted/userinterface#...

Re: Integrated Terminal Performance Improvements

#28

Post by celim307 »

Waterluvian wrote: post #19

What's the case for using the terminal in VSCode? I use a modern multitasking computer where VSCode is in one area or screen and my terminal in another (and other things in others). By using my own terminal I get to keep everything custom about that terminal rather than having another one. Surely there's reasons that I'm missing? Edit: thanks for all the responses. A lot of great new things I didn't think of before!

For me it's keeping things organized in my mindspace. When I tab to a VS window, it has my code right there alongside it's relevant git cli and server output. Helpful when I'm running a lot of services locally or simultaneously adding code to a package and using it locally with npm link in a different codebase, before publishing.

With something like iterm it's a little more sluggish to remember which tile corresponds to which codebase, especially when it's spitting out a lot of logs and obscures it's current directory

Re: Integrated Terminal Performance Improvements

#29

Post by batmansmk »

koolba wrote: post #23

> Misaligned characters: Due to many monospace fonts not being strictly monospace for some Unicode characters, this could lead to situations like the one seen on the right-side of the image below: (image) What are they referring to? I've been staring at the pic for nearly a minute and can't see anything misaligned.

Top right and bottom right corners of the green box.

Re: Integrated Terminal Performance Improvements

#30

Post by w0utert »

seanmcb wrote: post #21
w0utert wrote: post #11

I really wish Microsoft had used a different platform to build VS code on, like C#/Mono, Java, anything except Javascript/Electron basically. I just started using VS code for C++ development, trying to switch from Vim, an I basically like everything about the concept, but the execution and quality/polish of the software is mediocre at best. At least three times a day random stuff breaks: code completion stops working…

Hi @w0utert 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.
Post reply on HN