So I don't clog up the rest of the comment thread I'll add my atom/vscode/sublime thoughts here. I've been a long time sublime user and found it very very diff

So I don't clog up the rest of the comment thread I'll add my atom/vscode/sublime thoughts here. I've been a long time sublime user and found it very very difficult to switch to anything else, mainly for performance reasons. But I decided to give atom and vscode a real try for a couple of weeks each. These are my findings and results. I started with VScode when dotnet-core was officially released for OSX. The debugging features, performance, and usability were awesome. I was going to stop right here and jump to vscode except for these reasons. - Tabs. I know they're coming, but every time I had to go looking for the correct file I was ripped out of my train of thought. - Shortcuts. They're completely different to sublime/atom and I didn't feel like learning a bunch of F-key shortcuts. So I decided to give atom another go. Right off the bat I had a very nice looking editor. I appreciate the settings UI that isn't just a text file. The project view on the left is way better than sublime's. A major pain point of mine with sublime was opening a file with CMD + T, but then being unable to find it in the project view on the left. Atom has a reveal in project feature that expands the tree and focuses the file. The git status indicators on each file are nice too. The shortcuts are similar enough to sublime that there's no learning curve. Atom has a lot of really nice quality of life improvements over sublime text. Startup is really slow. Incremental search is really slow. When I'm viewing large text files I still load them up in sublime text. But for the majority of my coding now, I'll be using atom. I do quite a bit of C# development in a windows VM, so I might fire up vscode for that use case if dotnet core becomes an option for the app I'm working on.