4 ms·
I'm usually in VS, where tabs are dominant, but I've used just about every editor under the sun and I've started to realize tabs are a pretty horrible UI. The f
by jasonkostempski 10y ago
I'm usually in VS, where tabs are dominant, but I've used just about every editor under the sun and I've started to realize tabs are a pretty horrible UI. The first time I was forced to think outside the tab was with XCode (it has them but they don't behave anywhere near the same). I despised it at first but eventually started preferring the "assistant editor" window and using tabs to separate areas of concern. I've used Vim a lot too and I used to keep trying to make it do the tab per file thing until I saw what XCode was going for and started using it more like that and have been much happier with it. In VS Code I think the working files list on the left is a far easier to read and navigate that tabs could ever be and Ctrl+Tab still works as expected. I'm hoping VS adopts some window layout ideas from VS Code and some other places too.
- bmurphy1976 10y agoA major change that disrupts a well honed workflow should have a significant upside to be worth the investment. As far as I'm concerned, the working files list does not provide enough of an upside to justify breaking my workflow, which sure is one big downside. The working files list is a perfectly reasonable solution to the problem for those who want it. I see no reason why it should be removed. That said, by not supporting an alternate tab-based workflow, VSCode is preventing a good chunk of devs from adopting it as their daily driver.