Atom vs Brackets: What are the differences?
Developers describe Atom as "A hackable text editor for the 21st Century". At GitHub, we're building the text editor we've always wanted. A tool you can customize to do anything, but also use productively on the first day without ever touching a config file. Atom is modern, approachable, and hackable to the core. We can't wait to see what you build with it. On the other hand, Brackets is detailed as "A modern, open source text editor that understands web design". With focused visual tools and preprocessor support, Brackets is a modern text editor that makes it easy to design in the browser. Try Creative Cloud Extract (preview) for Brackets for an easy way to get clean, minimal CSS straight from a PSD with no generated code.
Atom and Brackets can be primarily classified as "Text Editor" tools.
Some of the features offered by Atom are:
- Atom is a desktop application based on web technologies
- Node.js integration
- Modular Design- composed of over 50 open-source packages that integrate around a minimal core
On the other hand, Brackets provides the following key features:
- Code Hints from a PSD
- Inline Editors
- Live Preview
"Free" is the top reason why over 514 developers like Atom, while over 46 developers mention "Beautiful UI" as the leading cause for choosing Brackets.
Atom and Brackets are both open source tools. It seems that Atom with 49.2K GitHub stars and 12.1K forks on GitHub has more adoption than Brackets with 29.9K GitHub stars and 6.42K GitHub forks.
Lyft, Typeform, and PedidosYa are some of the popular companies that use Atom, whereas Brackets is used by WorldGaming, 4RWeb Interactive, and LifeChurch.tv. Atom has a broader approval, being mentioned in 836 company stacks & 725 developers stacks; compared to Brackets, which is listed in 36 company stacks and 32 developer stacks.
What is Atom?
What is Brackets?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Brackets?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:
- your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
- it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
- I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen
The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.
I used to be a hardcore fan of Sublime Text. I am not a coder so I only use it for quick scripts or to play around. I don't spend hours and hours a day within Sublime Text though. However, last year (2017) a colleague, a developer, showed me Atom - a game changer. Love the customisation and overall feel while coding. Again, I am not spending hours a day within but I've noticed I've spent more time playing around and coding stuff since i've moved to Atom.
Before switching to Visual Studio Code, I used Atom. In contrast to Atom, Visual Studio Code is faster, provides more built-in features, and fails less often.
I started using Visual Studio Code because Atom was oftentimes extremely slow on even basic tasks, and there were bugs that could freeze the entire window if you dragged something the wrong way. Atom also didn't have as many integrated features as Visual Studio Code, so I had to find all of the best extensions. Even with the right tools available, many language extensions were frequently buggy, ineffective, and slow.
Both are very good! But I started with Visual Studio Code when I started to work with AngularJS 4. I tried to use Atom too, but at that time Atom did not have good Angular plugins, in the other side VS Code has nice plugins for Angular. I do not know how is Atom now a days about this, but I think that it must have evolved.
Have been a Visual Studio Code user since just after launch to the general public, having used the likes of Eclipse and Atom previously. Was amazed how mature it seemed off the bat and was super intrigued by the bootstrapped nature of it having been written/based on Electron/TypeScript, and of course being an open-source app from Microsoft. The features, plugin ecosystem and release frequency are very impressive. I do dev work on both Mac and Windows and don't use anything else now as far as IDEs go.
More than year ago I was looking for the best editor of Angular 2 application and I've tried Visual Studio Code and Atom. Atom had performance issues that put me off completely to use it again. Visual Studio Code became my main editor #Typescript files (and partly editor of #Java files). I'm happy with Visual Studio Code and I've never look back on Atom. There wasn't any reason to try Atom again, because Visual Studio Code fulfills my requirements very well. I use it for editing of TypeScript, #HTML, #Sass, JSON, Docker and Markdown.
Visual Studio Code became available around the time my Atom editor started frustrating with hitching and slowdowns. It was likely some plugin I had installed, but a similar setup in Visual Studio Code ran just fine.
Since then they've made massive improvements, and turned it into an excellent IDE overall. I use only a fraction of its functionality, but unless you use some very obscure language, you're likely to find support for it.
Even out of the box it already supports much of what I need, and it now even recommends suitable plugins in many situations.
A few months ago, I decided I would try Visual Studio Code. I resisted for so long because I knew I would love it and would then have to find alternative extensions for the ones I have installed in Atom. Fast forward to today and I'm kicking myself for not doing it sooner.
Extensions that I use:
What VSCode extensions do you use? 👇
I use Atom because it's been around long enough to have plugins for everything. It is very unlikely that there isn’t a plugin for your favorite language. It’s super easy to install plugins and packages (or to write your own!). The editor defaults are great: it’s the best default setup I’ve ever seen for a text editor. One can download this thing and get working immediately.
At the end of the day, most modern text editors are great. I do love Visual Studio Code as well! I often find myself switching between the two for no other reason other than just because.
We use Visual Studio Code because it allows us to easily and quickly integrate with Git, much like Sublime Merge ,but it is integrated into the IDE. Another cool part about VS Code is the ability collaborate with each other with Visual Studio Live Share which allows our whole team to get more done together. It brings the convenience of the Google Suite to programming, offering something that works more smoothly than anything found on Atom or Sublime Text
I use Visual Studio Code because it is a super flexible code editor that can be customized to function like a full IDE. It has great git and terminal integrations out of the box compared to Atom and Sublime Text
It has so many extensions and boots up pretty fast even with all my extensions.
Feel free to checkout my settings: VS Code Settings
I have chosen Visual Studio Code after testing a lot of other editors like Atom, Sublime Text (with legal license), Vim or even Notepad++ because it is the sum of all their virtues and none of their defects. It's fast, it has all the tools and plugins I need to work, and it's pretty and very good optimized. It has what I need to work and nothing more. And the main plugins works like a charm. Developing for React or Flutter is amazing. Even the TypeScript plugin works great. I like how IntelliSense works, and all the extra tools to code remotely using #ssh, access #RESTfulAPI or event manage projects or collaborating remotely. Thanks #Microsoft for Visual Studio Code.
Atom is Github's text editor, at the time of this writing it's still in private beta.
It uses Chromium Embedded at it's core, and integrates with node.js. It provides easy access to extensibility features, including an autocompletion API.
Everything you see in your editor window is in a DOM. This is akin to Codemirror or Ace. Meaning you get both the benefit of debugging your extensions with a webkit console, and the harm of having dom overhead everywhere in your text buffer.
Since the main editor is essentially a browser, you can also preview html directly in the same window. At the time of this writing you can live preview your markdown like with other markdown editors based on similar technology. Currently it's not possible to preview other html pages in there, but it's likely that this is in the works.
Atom is clearly an early look at a new code editor and much work remains to be done to produce a good community, a wide array of plugins as well as improving upon the performance of the product.
That aside, GitHub clearly cares about this product and is working hard to produce something that may well be great. Feedback has been responded to promptly and updates are rolling out to address issues.
The process of producing and publishing plugins is very smooth with a good set of tools to assist in the progress. Documentation is still in progress.
There are still performance problems with larger files and really large files can't be loaded at all. However, this is still a beta, so it remains to be seen what happens here.
Atom is a great editor that feels very familiar if you're used to Sublime Text. The UI is almost copied verbatim and you will feel right at home.
It comes with a package manager built right into the system, with plugins as a first class citizen.
All of this greatness comes to a screeching halt though:
- You cannot open files larger than 2MB.
- It's built on Webkit so it's slow as molasses.
I use atom in every bit of programming from markup, styling to customised autocomplete for python and JS. Nuclide theme is an awesome tool for React Native which is light version of both Android Studio and XCode.
It is truly a hackable editor but along with that it's very slow and takes lots of memory.
Have gone from TextMate to Sublime and now to Atom - in love with it - it's open source, it's got a massive contributor community, and it works well. (A bit slow and bogged down with lots of files, but we'll all make it faster over time)
We are using Atom on many of our workstations to be able to have a configurable editor available. It's also provisioned to our Remote Desktops to be able to work with the same tools available as on the Workstations.
Atom is the most aesthetically pleasing script editor out there period. With all the useful extensions and the unbeatable integration with GitHub, you must give this a try!
Self taught : acquired knowledge or skill on one's own initiative. Platform: OSX 10.8 or later, Windows
My primary Text Editor. Custom snippets help cut down on boiler plate and keep my work flow efficient.
Rapid small editions on code and markdown texts. Greate for simple projects with not so many files.