Atom vs Visual Studio IDE

• Atom is highly customizable and allows for various themes and extensions that can make your code easier to read.
• Atom has many code hinting features that allow users to write faster and integrate with services likeLINT that can clean up your code once your done to meet your internal teams style choices.
• It's very fast and manages projects well - Accessing other files within a related folder(s) is very easy and intuitive.
• It's free!

Read full review

• Since Microsoft offers a free Community Edition of the IDE many of our new developers have used it at home or school and are very familiar with the user interface, requiring little training to move up to the paid, enterprise-friendly editions we use.
• The online community support for Visual Studio is outstanding, as solid or better than any other commercial or open-source project software.
• Microsoft continuously keeps the product up to date and has maintained a history of doing so. They use it internally for their own development so there is little chance it will ever fall out of favor and become unsupported.

Read full review

• Due to some default settings, when I opened the file in Atom and commit it on Git it shows almost every line is changed so my PR is looking too big/ugly.
• I think omitting the empty spaces should not be the default setting.
• Performance needs some attention.

Read full review

• Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
• Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.

Read full review

• There really was no ROI for us using or not using Atom, positive or negative.
• The only positive thing I can think of is that I got some face time with the software and realized it just was not for me.

Read full review

• Since we're currently using the community edition, there was no expense to implement Visual Studio which meant an instant ROI.
• Because of the capabilities Visual Studio has to track large projects we've benefited from improved productivity using this IDE. We don't have to use multiple tools to build out a project.
• I don't consider it a negative, but to use a tool like Visual Studio you have to invest the money in buying hardware that's fast enough to run the IDE. That probably goes without saying.

Read full review