Atom is great for simple HTML coding. It's fast, has intuitive shortcuts and several options. I particularly love the "convert spaces to tabs" function that I haven't seen in other editors.
I'm not sure how it would fair in more serious web development today, if there are plugins for live updates of the page you are working on...
But the problem is that it has been discontinued so you know there are no new features or fixes coming through.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
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.
Well Atom is open source so the re-new is a no brainer. The only way I would stop using Atom is if the developers somehow made it not function well. Or, if the project got forked to a commercial version or something. Or, there could be the case that development stops or that it was not updated on this or that platform
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
I give Atom a 9 because it is one of the most modern text editors built with JavaScript intentionally to allow the editor to be changed and modified with custom functionality that a team may need. I think I would otherwise give atom an 8 due to support, but it gets a 9/10 because of the extensibility/plugin capability.
Atom has an active forum and a Slack group where you can ask technical questions. Occasionally, the authors will pop in to answer a few questions here and there, but most of the time, its other helpful users who will assist you. Though they aren't the most knowledgeable, they are at least timely.
As for plugin support, that differs with each plugin, but as I mentioned before, many plugins are no longer maintained.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Our company likes to keep things open, and we don't want to prevent developers from customizing their environment the way they want. Atom seemed to be a lot more open than our existing tools and has good community support on pretty much any programming language. This can create some confusion since adding too many extensions or customizing can make the tool slower than it is supposed to be.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
The tool we use when we need quick fixes. Allows fast, reliable scripting to fix urgent problems in our applications.
When applications grow from 5-10 files to 100's, they need to be migrated to a heavier-duty IDE. This can be cumbersome and quite annoying, but is necessary to maintain code integrity on such a large scale (since it cannot be done with the limited default toolset of Atom).
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
