What does HackerNews think of atom?

:atom: The hackable text editor

Language: JavaScript

#1 in Atom
#5 in Electron
#12 in JavaScript
#10 in Linux
#8 in macOS
#7 in Windows
I'm surprised that nobody here mentioned Atom [1]. IIUC, Atom was designed to be hackable like Emacs.

A successor to Atom is Pulsar [2].

[1] https://github.com/atom/atom

[2] https://pulsar-edit.dev/

One difference is that you can continue using your old Atom install, and if it had been "extinguished", you couldn't[1]. The other difference is that EEE was largely about interoperable protocols, not what one person could do with one program - it was about TCP/IP and SMTP and HTML and trying to take those over to Microsoft's benefit[2].

> "And blaming it on the end-user because they fail to pick up a massive product like Atom and develop it themselves seems disingenuous at best.

Yes, welcome to the elephant in the room of Open Source, 'many eyes makes bugs shallow', and the other pretenses we don't question. But at least the principle stands - you can still get the Atom source code[3] and pay someone as a contractor to change it for you, employ some people to work on it, start up a foundation, beg someone. Compared to a closed source program built on patented algorithms when the company shuts down and nobody can practically or legally improve it, or compared to a multiplayer game with online servers which the company shuts down and you can't use the game ever again, it is different.

[1] If you think it's impossible for Microsoft to reach into your Linux machine and take your Atom editor away, you'll see why EEE is a moral-panic rather than a real thing which could ever happen.

[2] you know, like Google actually does with HTML/Chrome strong-arming through Google-custom extensions, AMP pages, and the like. You'll see that this still hasn't resulted in other people being unable to make browsers or webservers or web-like protocols (Gemini).

[3] https://github.com/atom/atom

You can also take a look at Atom. Which is open source code editor (similar with Visual Studio Code). https://github.com/atom/atom
Atom is open source though. One company can not decide to kill it.

https://github.com/atom/atom

GitHub: Atom | Full-Time | San Francisco, Boulder, Amsterdam, REMOTE, VISA

Come help us make Atom faster! Get paid to work on an open source editor used by over a million people every month.

https://atom.io | https://github.com/atom/atom

Some things we're focused on for the next six months:

  * Core Experience/Performance 
  * Git/GitHub integration 
  * Language integration: better auto-complete, syntax highlighting, and debugging 
  * Windows-specific features and fixes
Apply at https://jobs.lever.co/github/baaa9a2c-c249-4d06-b73f-e9bee1a...
> Now there are two reasons I can think of this happening

They are also churning at a pretty insane rate due their release schedule. I did a very basic analysis of their repos at

http://gitsense.github.io/blog/motion-bubble-charts.html

And this is the churn for this month in their master and 8-7-stable branch

http://imgur.com/PfyFrzS

I also included the https://github.com/atom/atom master branch (blue line) for comparison.

In order to get a better picture what what's going on, I'll need to cross reference the churn to security issues, but this isn't something my tool will support until later in the year.

> Avoid CoffeeScript. Most of its better features are now in ES6, a standard.

This argument against CoffeeScript isn't very objective. One of CoffeeScript's best features is the minimalistic and expressive syntax.

"CoffeeScript (#6) appears dramatically more expressive than JavaScript (#51), in fact among the best of all languages."[1]

"CoffeeScript is #1 for consistency, with an IQR spread of only 23 LOC/commit compared to even #4 Clojure at 51 LOC/commit. By the time we’ve gotten to #8 Groovy, we’ve dropped to an IQR of 68 LOC/commit. In other words, CoffeeScript is incredibly consistent across domains and developers in its expressiveness."[1]

Using the author's train of thought I could state: "Avoid Bluebird[2]. Most of its better features are now in ES6 promises, a standard."

Yes promises are in the ES6 standard, but that's not the best feature of bluebird. There were and are many promise based libraries, but bluebird was built for unmatched performance. One will use it if performance matters.

Even today it's faster than the native implementations of promises [3].

> Tooling (such as CoffeeLint) is very weak.

Maybe because, as it turns out, in CoffeeScript you don't need a lot of tooling. Why would that be a bad thing?

> Electron is the foundation of the great Atom editor and can be used to make your own applications.

Atom is written in CoffeeScript [4].

[1] http://redmonk.com/dberkholz/2013/03/25/programming-language...

[2] https://github.com/petkaantonov/bluebird

[3] http://programmers.stackexchange.com/questions/278778/why-ar...

[4] https://github.com/atom/atom

Yes we get all of the whatnots ;)

The developers on this project are using Atom https://github.com/atom/atom/ for their day to day Dart development. They are contributing to the Dart plugin https://github.com/dart-atom/dartlang, and implementing a Flutter specific plugin https://github.com/flutter/atom-flutter-dev. The Dart SDK https://github.com/dart-lang/sdk provides the basic source code analysis tools. All of these projects are open source, on github, and see regular commits.

You mean the source code? I compiled it from their github.

https://github.com/atom/atom

There are build instruction for Linux in README. https://github.com/atom/atom \nPlus I had to fix libudev problem with this https://github.com/atom/atom/issues/1814#issuecomment-423253... Other than that it had no problems to build or launch.
The atom repo https://github.com/atom/atom has installation instructions for Linux and Windows. Just installing it on Ubuntu to give it a try.
You should read the README before whining. Linux and Windows are also supported.

https://github.com/atom/atom

There are build instructions for Linux and I think even Windows as well. I think Ubuntu is currently the main target on the linux side.

Edit: Just double checked and there are Windows build instructions at https://github.com/atom/atom. Although I haven't actually tried to follow them, so I'm not sure if they end in a usable build.