6 ms·

Who even use VScode professionally? I'm still waiting for multi-monitor window support, which not gonna happen, IIUIC. Mentioned this in VScode subreddit, I go

Who even use VScode professionally? I'm still waiting for multi-monitor window support, which not gonna happen, IIUIC. Mentioned this in VScode subreddit, I got downvoted to hell, because clearly nobody needs IDE's windows in different monitors.

3np 4y ago
Sounds like something that should be handled by your WM. Expecting your IDE to handle "multi-monitor support" (precisely what functionality are you even expecting here..?) sounds less professional, if anything :P
- lozenge 4y ago
  I think they mean tearing an editor (or other panel) out into another window to move to their other monitor. Currently you can open another window, but it comes with its own explorer, terminal, problems, test runner, etc. Soon you'll have the same file opened twice in different screens, and... bleh.
  - dx034 4y ago
    But you can just drag it across two screens and divide it up along the border? From my experience that works fine as long as your screens have the same resolution.
    - lozenge 4y ago
      True, you can divide the editor into two (or more) splits, and also divide the bottom part (Terminal/Debug Console/Problems). If you're the type that doesn't move windows around often, that could work.
- sjnsjks 4y ago
  Perhaps there is some hidden configuration for this. But did you try to have separate windows of vscode on monitors with different DPI or set different scale manually? There is a shared thing going on between running instances. I can't have one window 100% and other 150%.
  - 3np 4y ago
    Join the Wayland side. We have cookies (and multi-DPI or whatever the kids call it).
jhugo 4y ago
Huh? I am not a big fan of VSCode (for other reasons [0]), but I have its windows on multiple monitors all the time. Works fine. Can't even understand how a program could stop that working. [0] It chews enormous amounts of CPU and RAM, and periodically gets into a state where it won't open the "Open file" dialog for unknown reasons. And occasionally renaming a file brings up something like "Running 'Rename file' participants..." which hangs for 15+ minutes. Absurd.
- can16358p 4y ago
  Interesting. What languages/plugins/processes are you using? I'm a TypeScript/React/React Native dev and Vscode is butter smooth with very minimal CPU and RAM usage (after offsetting the Electron overhead).
  - jhugo 4y ago
    Why would you offset the Electron overhead? Plenty of other editors don't use web tech, so it doesn't make sense to give VSCode a free pass for choosing to use it. Anyway, I tried running with no plugins for a while, and still had the problems (open file dialog failing, and random occurrences of "running file rename participants" hanging for a long time) occasionally. It happens sporadically on both my M1 MacBook Air running macOS and my Threadripper workstation running Linux, even with no shared config and only editing local files, so I am pretty sure it's just buggy VSCode. I found numerous old bug reports about similar issues. All closed without resolution after being ignored for months. Edit: oh, and about the CPU and RAM, this is mostly an issue on my MacBook — VSCode is the only software I have ever found that will make it noticeably lag sometimes. I can always close it and open it again with the same files and it will work perfectly for another few days.
yanchep 4y ago
Interesting, I never hat this specific problem. We use VSCode(ium) in two ways: - Locally on the double-wide screens on Linux, no multi-monitoring needed. - On Windows Servers in tiny and ugly remote desktops of our customers, no multi-monitor available.
ActorNightly 4y ago
Sans for Java, for which IntelliJ IDEA still holds a little bit of an edge in terms of syntax highlighting, lots of people are moving to VSCode. Besides all the nice little features (like jumping through code, markdown render, e.t.c) it has 4 big advantages. First, VSCode remote SSH extension is EXTREMELY useful - any computer you can SSH to you can edit code directly on with any extension. Secondly, terminal integration is super nice. You can configure keybinds specifically for the terminal (and in general, they are pretty well set up default). So for example if you are using remote SSH extension from windows to linux, the terminal functions just like under native Linux. Thirdly, for data science dev, native Jupyter support is super nice. Fourthly, the remote SSH integration also works extremely well with Windows/WSL2, which is arguably the best way to have a "dual boot" system today. You get the widest range of software/games that you can run, with almost no drawbacks in comparison to running native Linux. You can do all your dev in WLS2 nicely with VSCode, just like you would under Linux, including things like docker, CUDA for ML, e.t.c. Even graphical linux apps work now.
- dx034 4y ago
  VSCode with remote ssh is the main reason I'm not on Linux anymore. I always liked Windows more for everyday use (I know that's a rather unpopular opinion here) but needed Linux for development work. With remote SSH it feels like I'm developing on Linux (I use a small VM for that) without having to change my OS. Plus, it makes switching between machines much easier.
  - the_only_law 4y ago
    > VSCode with remote ssh is the main reason I'm not on Linux anymore. WSL mostly did it for me. I can go from playing games on the platform that’s received the most attention (which is nice when a Linux port is broken or for some reason doesn’t play nice with proton) to programming and hacking in a familiar environment. The exception is when I’m screwing with Linux specific hardware, as WSL doesn’t have USB or PCIe pass through afaik.
- mekster 4y ago
  How is the extension better than upload-on-save from an editor and using a dedicated terminal app?
can16358p 4y ago
> Who even use VScode professionally? I do. And countless of developers I know, who were perfectly professional when I last checked. Many developers don't need multi-monitors. I understand if you need/want it but calling "who even use Vscode professionally" is kind of unthoughtful.
upupandup 4y ago
Lots of people who don't want to pay $199/year for JetBrains IDE You are being downvoted for being close minded and half baked assumptions

3np 4y ago

Sounds like something that should be handled by your WM. Expecting your IDE to handle "multi-monitor support" (precisely what functionality are you even expecting here..?) sounds less professional, if anything :P

lozenge 4y ago
I think they mean tearing an editor (or other panel) out into another window to move to their other monitor. Currently you can open another window, but it comes with its own explorer, terminal, problems, test runner, etc. Soon you'll have the same file opened twice in different screens, and... bleh.
- dx034 4y ago
  But you can just drag it across two screens and divide it up along the border? From my experience that works fine as long as your screens have the same resolution.
  - lozenge 4y ago
    True, you can divide the editor into two (or more) splits, and also divide the bottom part (Terminal/Debug Console/Problems). If you're the type that doesn't move windows around often, that could work.
sjnsjks 4y ago
Perhaps there is some hidden configuration for this. But did you try to have separate windows of vscode on monitors with different DPI or set different scale manually? There is a shared thing going on between running instances. I can't have one window 100% and other 150%.
- 3np 4y ago
  Join the Wayland side. We have cookies (and multi-DPI or whatever the kids call it).

jhugo 4y ago

Huh? I am not a big fan of VSCode (for other reasons [0]), but I have its windows on multiple monitors all the time. Works fine. Can't even understand how a program could stop that working. [0] It chews enormous amounts of CPU and RAM, and periodically gets into a state where it won't open the "Open file" dialog for unknown reasons. And occasionally renaming a file brings up something like "Running 'Rename file' participants..." which hangs for 15+ minutes. Absurd.

can16358p 4y ago
Interesting. What languages/plugins/processes are you using? I'm a TypeScript/React/React Native dev and Vscode is butter smooth with very minimal CPU and RAM usage (after offsetting the Electron overhead).
- jhugo 4y ago
  Why would you offset the Electron overhead? Plenty of other editors don't use web tech, so it doesn't make sense to give VSCode a free pass for choosing to use it. Anyway, I tried running with no plugins for a while, and still had the problems (open file dialog failing, and random occurrences of "running file rename participants" hanging for a long time) occasionally. It happens sporadically on both my M1 MacBook Air running macOS and my Threadripper workstation running Linux, even with no shared config and only editing local files, so I am pretty sure it's just buggy VSCode. I found numerous old bug reports about similar issues. All closed without resolution after being ignored for months. Edit: oh, and about the CPU and RAM, this is mostly an issue on my MacBook — VSCode is the only software I have ever found that will make it noticeably lag sometimes. I can always close it and open it again with the same files and it will work perfectly for another few days.

yanchep 4y ago

Interesting, I never hat this specific problem. We use VSCode(ium) in two ways: - Locally on the double-wide screens on Linux, no multi-monitoring needed. - On Windows Servers in tiny and ugly remote desktops of our customers, no multi-monitor available.

ActorNightly 4y ago

Sans for Java, for which IntelliJ IDEA still holds a little bit of an edge in terms of syntax highlighting, lots of people are moving to VSCode. Besides all the nice little features (like jumping through code, markdown render, e.t.c) it has 4 big advantages. First, VSCode remote SSH extension is EXTREMELY useful - any computer you can SSH to you can edit code directly on with any extension. Secondly, terminal integration is super nice. You can configure keybinds specifically for the terminal (and in general, they are pretty well set up default). So for example if you are using remote SSH extension from windows to linux, the terminal functions just like under native Linux. Thirdly, for data science dev, native Jupyter support is super nice. Fourthly, the remote SSH integration also works extremely well with Windows/WSL2, which is arguably the best way to have a "dual boot" system today. You get the widest range of software/games that you can run, with almost no drawbacks in comparison to running native Linux. You can do all your dev in WLS2 nicely with VSCode, just like you would under Linux, including things like docker, CUDA for ML, e.t.c. Even graphical linux apps work now.

dx034 4y ago
VSCode with remote ssh is the main reason I'm not on Linux anymore. I always liked Windows more for everyday use (I know that's a rather unpopular opinion here) but needed Linux for development work. With remote SSH it feels like I'm developing on Linux (I use a small VM for that) without having to change my OS. Plus, it makes switching between machines much easier.
- the_only_law 4y ago
  > VSCode with remote ssh is the main reason I'm not on Linux anymore. WSL mostly did it for me. I can go from playing games on the platform that’s received the most attention (which is nice when a Linux port is broken or for some reason doesn’t play nice with proton) to programming and hacking in a familiar environment. The exception is when I’m screwing with Linux specific hardware, as WSL doesn’t have USB or PCIe pass through afaik.
mekster 4y ago
How is the extension better than upload-on-save from an editor and using a dedicated terminal app?

can16358p 4y ago

> Who even use VScode professionally? I do. And countless of developers I know, who were perfectly professional when I last checked. Many developers don't need multi-monitors. I understand if you need/want it but calling "who even use Vscode professionally" is kind of unthoughtful.

upupandup 4y ago

Lots of people who don't want to pay $199/year for JetBrains IDE You are being downvoted for being close minded and half baked assumptions