With experimental options turned on it saves the latest file I searched, but if I change the search a little it will not be recognised anymore and will suggest strange results. Fuzzy Finder does not work properly for me.I have put a command in the configuration file so it always opens Ruby files as Rails files, but I think this is not ideal. It does not recognise Rails files, opening them always as Ruby files.It has a very good dark theme with a comfortable design.Very good support for linters, marking suggestions in place.It strips white-spaces and adds a blank line at the end of the file when saving.In macOS you can use the tab key to shift lines of code to the right without affecting snippet generators.It uses a dedicated tab for this and updates the results while you change the code. For instance, rails-transporter, that though CTRL-R and then a C or a V you can navigate between the controller and the view. There is a huge community helping to implement new features.I’m going to describe the positive and negative points about Atom, but they are also applicable to Visual Studio Code. Everything seemed familiar and easy-going to me.īeing free is a major boost for its success, and coming from GitHub and Microsoft gives a warm feeling of “being at home”.

They seem to be the natural successors to Sublime Text, so I used them for an entire project and I felt very comfortable. Atom has a great GitHub integration out of the box, but Visual Studio Code can do the same with extensions. I find both very similar, and it depends on which one you like most, or feel more comfortable with. Atom is an open source editor created by GitHub, and Visual Studio Code is a very similar one created by Microsoft.īoth are based on Chrome technologies and they are very customizable.

Visual studio code vs atom 2017