Live data from Hacker News

Git and GitHub Integration Comes to Atom

blog.atom.io

31–40 of 112 posts

Re: Git and GitHub Integration Comes to Atom

#31
I tried it, because I'm trying to convince a colleague to use markdown and git for a collaborative project. This person lives mainly in the MSword world, so I thought atom might be a good choice. In testing it, I found the git interface was simple for me, having used git for years and therefore knowing what "staged" means. However, the interface will be confusing for my colleague. It would be great if the atom folks could make a 30-second video of the workflow, a bit like Apple has done for taking photos of different types. Failing that, it will be me on the phone with my colleague, telling them what to click and when. I think the atom folks could have done this better. Maybe they should highlight the "next most likely" action at any time.

Re: Git and GitHub Integration Comes to Atom

#32
post #5

Bundling these features by default is bad for Atom. It changes Atom from an editor to an advertisement. Maybe Github dwarfs the competition but boxing them out of the editor is unnecessary. This smells like bundling IE with Windows 98.

On the other hand this will Github an incentive to keep on improving Atom. Maybe someone has finally figured out how to monetize an editor. I hope so, cause the current ecosystem of editors is a mess of half baked solutions.

Why use one of those half baked solutions when vim already exists?

Re: Git and GitHub Integration Comes to Atom

#33
post #5

Bundling these features by default is bad for Atom. It changes Atom from an editor to an advertisement. Maybe Github dwarfs the competition but boxing them out of the editor is unnecessary. This smells like bundling IE with Windows 98.

On the other hand this will Github an incentive to keep on improving Atom. Maybe someone has finally figured out how to monetize an editor. I hope so, cause the current ecosystem of editors is a mess of half baked solutions.

Why use one of those half baked solutions when vim already exists?

Re: Git and GitHub Integration Comes to Atom

#35
Just today the author of the "merge-conflicts" package for Atom emphasized that his plugin is depcrecated because Atom 1.8 will have that feature included by default.

https://github.com/smashwilson/merge-conflicts/commit/f61950...

https://github.com/smashwilson/merge-conflicts/blob/master/d...

Re: Git and GitHub Integration Comes to Atom

#38

This looks like a fantastic development, but I worry about performance. Atom is already pretty sluggish, I would rather see performance upgrades before new features. Maybe they're not correlated.

Performance has been a key focus of the last few releases. 1.17, the stable release also being released today, has a major jump: http://blog.atom.io/2017/04/18/improving-startup-time.html

Has memory usage also been a focus? I got scared off from exploring Atom a month ago by https://news.ycombinator.com/item?id=14141855

Re: Git and GitHub Integration Comes to Atom

#39

Has this been GH's eventual goal in developing this thing? Playing the long game?

The game has changed over time. They originally intended to charge for Atom. Then it became arguably the best free option, until VS Code came along.

I think a lot of us have moved from Atom/Sublime over to VS Code these days. Seems like lots more momentum and gobs of useful plugins that let me do my work.

Re: Git and GitHub Integration Comes to Atom

#40
post #5

Bundling these features by default is bad for Atom. It changes Atom from an editor to an advertisement. Maybe Github dwarfs the competition but boxing them out of the editor is unnecessary. This smells like bundling IE with Windows 98.

I've always considered Atom to be an advertisement for GitHub. The branding is unmistakable.
Post reply on HN