Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atom 1.36

blog.atom.io

Post reply on HN
Print view View original

51–60 of 75 posts

Re: Atom 1.36

#51

Post by asdkhadsj »

GordonS wrote: post #46
taylorlapeyre wrote: post #10

Prediction: If VS Code is the general do-it-all editor, Atom will become the GitHub editor. Atom is quickly ramping up feature integration with GitHub — seen here with integrating review comments inline with the code and the deep GitHub PR integration in general. GitHub and Atom have a very linked future, with GitHub planning to become more involved with the actual code-writing process. Atom will be the conduit thoug…

VS Code has had excellent git integration for a long time, as well as GitHub-specific integrations through an extension. Atom may have started the move towards lightweight (relatively) IDEs, but VS Code is undoubtedly the more popular one. Honestly, when I saw this post on HN I was quite surprised to see that Atom is still actively developed - if there's anyone reading this that prefers Atom over VS Code, I'd really…

Any thoughts on which is more friendly for (complex) plugin writing?

I've been wanting to add multi-cursor modal focused features to an editor for a while and I've been debating which editor would be the best one to write for. Thoughts?

Re: Atom 1.36

#52

Post by asdkhadsj »

citrusx wrote: post #25
xrd wrote: post #8

Earlier quoted context omitted.

Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.

Two things about VSC, in comparison to Atom, that are Done Wrong: 1) Extensibility. There's like a dozen times more friction involved in creating a plugin for VSC than for Atom. Atom was built to be as easy to change as a web app. They also created apm, which is sort of a clone of npm, for installing plugins. 2) Configurability. I can set personal keyboard shortcuts very easily, and in a way that's easily transportab…

Funny, I just commented on my desire to pick one of the top editors to write a complex plugin in.

While VSC sounds like a better editor, I want to write a multi-cursor, modal based editor with some UI tweaks. Ideally I'll use Xi long term, but I'd like a prototype working first. By your description, it sounds like I should stick to Atom for plugin development then?

Re: Atom 1.36

#53

Post by xrd »

mrspeaker wrote: post #37
ngrilly wrote: post #29

Earlier quoted context omitted.

Why? (compared to Sublime Text, Atom and VSCode)

I think it's a case of "you can't be told, you have to discover for yourself"... I've written it off a few times in the past. I thought Emacs was just a text editor - and after trying it a couple of times it seemed like a clunky relic with really stupid keybinds. This time when I tried it I started to realised that Emacs is a text editor like a saucepan is a popcorn maker: it can do it, but that's not the point. Once…

Do you use it as a debugger? For me, this was the difference in switching (when I am in a desktop environment) to VS Code. The debugger is just so powerful and I have no learned (despite using Emacs for 20 years) how to replicate that in Emacs.

Re: Atom 1.36

#54

Post by fartcannon »

equasar wrote: post #36
mdhughes wrote: post #33

Earlier quoted context omitted.

Strongly disagree. VS Code is a corporate tool IDE, which is dull and awkward to use as just an editor, and binary spyware in it "phones home" to its users' masters in Redmond. It's exactly what an MSDN subscriber would like, but dire for anyone else. Atom is fun. It's easy to configure in weird personal ways, get rid of parts you don't use, add your own plugins, change CSS as you like. There's an insane number of pl…

I think you missed the /s in your comment.

No need to insult whoever dislike your preferences.

Re: Atom 1.36

#55

Post by nobleach »

xrd wrote: post #8
wakeywakeywakey wrote: post #2

Prediction: I believe eventually MS will kill Atom or let development languish. People will complain that "MS is evil" and "look who they were in the past" and so on, but devs will go where the features are. VS Code is one of the finest examples of open source Done Right™, and while it owes something to Atom and Electron, this is pure open source darwinism.

Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.

Atom's Vim-Mode-Plus is amazing. VSC's vim plugin still has a way to go. (It's buggy, sometimes things just don't work) VSC is just not as extensible. If I want to change that bottom bar color, I have to set it in a config file, there's no hook to change it on the fly. If I want to navigate around the interface only via keyboard, it's not a pleasure. If I want to simply open a file in the file explorer on MacOS, I can't just hit ... and I don't think anyone's figured out a way around that yet.

Re: Atom 1.36

#56

Post by kraftman »

nnq wrote: post #32
guessmyname wrote: post #24

Earlier quoted context omitted.

> While Atom was Mac-only, VSCode was eating their lunch. It's too little, too late now. What do you mean? Atom has always been available for macOS, Windows, and Linux.

...ever tried actually using it on Windows? Like a year ago it got to ok-ish usable. A bit before that even on most Linuxes it had crappy performance. Again, I like Atom's hackability, and mainly avoid it because the ecosystem of plugins is so full of halfly owkring abandonware

First I've heard of this. I used Atom for a few years on windows and ubuntu without any issues except opening very large files.

Re: Atom 1.36

#57

Post by mrspeaker »

xrd wrote: post #53
mrspeaker wrote: post #37

Earlier quoted context omitted.

I think it's a case of "you can't be told, you have to discover for yourself"... I've written it off a few times in the past. I thought Emacs was just a text editor - and after trying it a couple of times it seemed like a clunky relic with really stupid keybinds. This time when I tried it I started to realised that Emacs is a text editor like a saucepan is a popcorn maker: it can do it, but that's not the point. Once…

Do you use it as a debugger? For me, this was the difference in switching (when I am in a desktop environment) to VS Code. The debugger is just so powerful and I have no learned (despite using Emacs for 20 years) how to replicate that in Emacs.

Nope, just lsp-mode (and Tide). Perhaps that'll take me another 20 years, but I've poured so many hours into debuggers and have never found them as useful as I think they should be. I'm probably "holding it wrong", and if so - I'll get there eventually!

Re: Atom 1.36

#58

Post by lucidone »

galfarragem wrote: post #48
GordonS wrote: post #46

Earlier quoted context omitted.

VS Code has had excellent git integration for a long time, as well as GitHub-specific integrations through an extension. Atom may have started the move towards lightweight (relatively) IDEs, but VS Code is undoubtedly the more popular one. Honestly, when I saw this post on HN I was quite surprised to see that Atom is still actively developed - if there's anyone reading this that prefers Atom over VS Code, I'd really…

VS Code, like Python, seems to be the second best tool on everything: it looks good but not as much as Atom, it's fast but not like Sublime or Vim, it's a lightweight IDE but not a full IDE.

I agree except for TypeScript and JavaScript - vscode is the best code editor I've experienced for both.

Re: Atom 1.36

#59

Post by lioeters »

bwha wrote: post #47
xrd wrote: post #8

Earlier quoted context omitted.

Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.

I was with Atom for years, switched to VS Code and feel in love (save for the find and replace as cited above, I still felt/feel Atom's is better than VS Code's) and stuck with it (VS Code) for months. The thing that made me switch back was that there was some combination of plugins I was using in VS Code (I think it was the VIM plugin and something else maybe) started freezing periodically and the whole editor would…

Funny, I had a similar (but somewhat opposite) experience: was a happy Atom user for some years until it started slowing down, freezing at increasing frequency; it was due to my having a massive tree of folders and files (top-level folder with all projects), with lots of symbolic and hard links. I had checked out VS Code a few times, but finally a couple months ago I was forced to make a switch - then pleasantly surprised how easy it was to migrate to it.

VS Code is not as hackable of an editor, but it comes with great sensible defaults out of the box. I gave up trying to fully customize it, settled with a few tweaks, and have been very satisfied with it as a daily driver. At least for my use case, it's been more reliable and performant than Atom.

The type hinting and "IntelliSense" is one of my favorite features (I'm sure Atom has a plugin for it). I think VS Code hits the sweet spot between an editor and a full-on IDE.

EDIT: Oh, I didn't see this in the article, but it seems Atom is addressing the exact issue I was having:

> The fuzzy finder’s project crawling performance has been improved dramatically by switching to a ripgrep-powered backend. This is most noticeable in projects with large numbers of files - for example, we measured a 14x speed boost in a project with 270K files.

Re: Atom 1.36

#60

Post by dual_basis »

PascLeRasc wrote: post #22
xrd wrote: post #8

Earlier quoted context omitted.

Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.

Personally I strongly prefer the UI of Atom, especially the iconography, settings menu, and visual layout. VS Code has a lot of extra features it shows by default that for me are just distracting. I love zen mode in Atom and the package ecosystem has been fantastic for me. Teletype is a killer feature, it's such a joy to use and makes me feel like I'm in the future. I've seen a lot of complaints about typing latency…

Psst - Microsoft owns Atom too...
Post reply on HN