> You can do that in any editor. Now lets say you want to open two more files D and E and have them split side by side. In vim, you can make a new tab and create that layout and then quickly switch between A/B/C & D/E. You cannot do that in VSCode or JetBrains. If you're in section B and open a new file, it will make tab inside section B.
Ah, I see yes. VSCode doesn't have nice buffers.
> When I'm using those editors, I find myself constantly creating and destroying layouts and it drives me insane. Let's say I'm editing some files and want to look at the diff of what I've done so far, in vim I can open a new tab and have diff|original.
How do you open the original file ? When I open the file again I end up with both buffers with the same modified content.
> In VSCode it will open the diff in one of my splits, and since it's a diff, it will be split in 2 as well. On my laptop I can't see anything if my diff|original only takes up half my screen, I have to resize/close splits at that point and then going back to what I was doing is more difficult.
Ah yes, when I stumbled into vscode git diff mode I get narrow panes lit up like a christmas tree. I do my git diffing in the terminal or in git-cola or whatever then.
> When I'm working on code and writing tests, I'll usually have my tests in one tab and the code in another. Or if someone asks me a question, I can make a new tab, start searching/reading code in there and then quickly go back to where I went. I find it extremely handy for context switching.
I usually end up with two instances of code running: one for backend/model/controller and the other for the views.
Ah, I see yes. VSCode doesn't have nice buffers.
> When I'm using those editors, I find myself constantly creating and destroying layouts and it drives me insane. Let's say I'm editing some files and want to look at the diff of what I've done so far, in vim I can open a new tab and have diff|original.
How do you open the original file ? When I open the file again I end up with both buffers with the same modified content.
> In VSCode it will open the diff in one of my splits, and since it's a diff, it will be split in 2 as well. On my laptop I can't see anything if my diff|original only takes up half my screen, I have to resize/close splits at that point and then going back to what I was doing is more difficult.
Ah yes, when I stumbled into vscode git diff mode I get narrow panes lit up like a christmas tree. I do my git diffing in the terminal or in git-cola or whatever then.
> When I'm working on code and writing tests, I'll usually have my tests in one tab and the code in another. Or if someone asks me a question, I can make a new tab, start searching/reading code in there and then quickly go back to where I went. I find it extremely handy for context switching.
I usually end up with two instances of code running: one for backend/model/controller and the other for the views.