I like Atom because it is simple and not too complicated. Configurable, full-featured, yet remains nimble. You can not beat the cost of Open Source, so this leaves software like BBEdit out in the cold. Atom is not as hardcore as Vim or Emacs. Less complicated than full IDEs …
Atom is not as great for Android development as Android Studio, as great for iOS development as Xcode, C# for Visual Studio, or even Java with Eclipse. Atom is less-preferred for any of those platforms for me. However, it is my preferred IDE for just about every other …
Director of Technology, Open Source Incubator Initiative
Chose Atom
Not listed is Vim, which is another free-form editor that is in the same product category. Vim and Emacs are both supported on more platforms and with lower systems requirements and similar versatility, but don't offer the ease of use (both being primarily keyboard-only …
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 …
Atom and Visual Studio Code are so similar it's hard to not compare them. But for new users, Atom is the clear winner. If you are looking for a clean interface, Atom is the winner. There aren't as many buttons and distractions in Atom which makes it very easy to just pick up …
Eclipse stands out with its feature set, reliability, and being completely free of charge. I have previously used NetBeans but had reliability issues with it, at least on Windows version. IDEA has modern UI and is significantly more user friendly than Eclipse; however, the free …
These are all very similar in what they can do, and so they all stack up very similarly. I personally have found that Eclipse did a little bit better when it came to programming with java and so that is why we went with it for the classes coding in Java.
Eclipse is the best IDE on the market for Java development. It has great error and warning handling, and many integrations with useful tools - debugger, sonarqube (static code analysis), Maven / Gradle / Ant, Tomcat / Wildfly / JBoss (web servers). The best part of eclipse is …
NetBeans is the closest competitor I've found to Eclipse for Java development. IntelliJ IDEA is good as well but it isn't free. NetBeans is a free competitor that has split the Java community, and a lot of it comes down to preference, like the famous vim vs. emacs wars. I would …
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.
I think that if someone asked me for an IDE for Java programming, I would definitely recommend Eclipse as is one of the most complete solutions for this language out there. If the main programming language of that person is not Java, I don't think Eclipse would suit his needs[.]
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.
While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.
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
I love this product, what makes it one of the best tool out in the market is its ability to function with a wide range of languages. The online community support is superb, so you are never stuck on an issue. The customization is endless, you can keep adding plugins or jars for more functionalities as per your requirements. It's Free !!!
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.
It has everything that the developer needs to do the job. Few things that I have used in my day-to-day development 1. Console output. 2. Software flash functionality supporting multiple JTAG vendors like J-LINK. 3. Debugging capabilities like having a breakpoint, looking at the assembly, looking at the memory etc. this also applies to Embedded boards. 4. Plug-in like CMake, Doxygen and PlantUML are available.
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 gave this rating because Eclipse is an open-source free IDE therefore no support system is available as far as I know. I have to go through other sources to solve my problem which is very tough and annoying. So if you are using Eclipse then you are on your own, as a student, it is not a big issue for me but for developers it is a need.
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.
The installation, adaptability, and ease of usage for Eclipse are pretty high and simple compared to some of the other products. Also, the fact that it is almost a plug and play once the connections are established and once a new user gets the hang of the system comes pretty handy.
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).
This development environment offers the possibility of improving the productivity time of work teams by supporting the integration of large architectures.
It drives constant change and evolution in work teams thanks to its constant versioning.
It works well enough to develop continuous server client integrations, based on solid or any other programming principle.
