Live data from Hacker News

Atom 1.29

blog.atom.io

21–30 of 120 posts

Re: Atom 1.29

#21
post #18

Earlier quoted context omitted.

Ok, that's nice to know. I know my initial comment probably came off as the stereotypical Hacker News sneer, but in my defense the picture, at least to me (having not used Atom for more than four years due to its poor performance when I tried it in the beta) makes it look like Atom was having issues maintaining a decent frame rate for the editing task shown, and is now able to provide this. Or, to put it another way:…

This is a perfect 'LOL hn' comment if I ever saw one.

Are you laughing at me, one of my comments in particular, or Hacker News in general?

Re: Atom 1.29

#22

I haven't used Atom for at least an year and a half now - After trying out Visual Studio Code I haven't looked back. Has the performance improved? Is it at the level of VS Code?

I had a similar experience with performance was an issue for me so I switched over. Never went to back to test any of their newer releases.

Re: Atom 1.29

#23
post #15

I haven't used Atom for at least an year and a half now - After trying out Visual Studio Code I haven't looked back. Has the performance improved? Is it at the level of VS Code?

The one reason I'm still using Atom is because of the remote editing experience with Nuclide + Watchman server-side. No other editor that I've tried comes even close (the connection drops, files get out of sync, new files don't show up, etc, etc) Given the huge number of people who work on remote servers, I find it surprising that proper solutions are still so hard to find. A "file system provider API" for VSCode is…

We just use Vim or Emacs over SSH in such cases, or if the connection is good enough over X/RDP.

Re: Atom 1.29

#24

I see a GIF of someone going deleting a couple lines of code, with a meter showing that the application is maintaining 60 FPS. Was this not something Atom could do before? It seems to me that the bare minimum should be maintaining 60 FPS while performing basic editing tasks…is there some nuance here I'm missing?

Then you probably don't appreciate what tree-sitter has to offer.

https://galois.com/blog/2017/12/tree-sitter-new-parsing-syst...

Re: Atom 1.29

#25

I haven't used Atom for at least an year and a half now - After trying out Visual Studio Code I haven't looked back. Has the performance improved? Is it at the level of VS Code?

I've bounced back and forth between Atom and VSCode - the main reason for me has been bugginess with prettier plugins. I've had more weird issues with the VSCode one, so I've leaned more on Atom.

Perf for VSCode is definitely much better though.

Re: Atom 1.29

#26
post #19

Earlier quoted context omitted.

We've also been in the same boat as you guys. Starting to just look into VSCode as an alternative, then immediately switching to it after realising the performance difference is like night and day. Since Atom doesn't provide anything that we can't install in VSCode as a plugin, there really is no reason to use Atom right now. The only problem I had with VSCode was the default interface, that I modified with plugins u…

I still use Atom mostly because of the default interface. Care to list the plugins that you used?

Of course. The most useful ones are the following:

- Bracket Pair Colorizer

- EditorConfig for VS Code

- ESLint

- Git Blame

- Material Icon Theme

- Path Intellisense

- Prettier - Code Formatter

- SCSS IntelliSense

- TSLInt

- Winter is Coming Theme by John Papa

Re: Atom 1.29

#27
post #15

I haven't used Atom for at least an year and a half now - After trying out Visual Studio Code I haven't looked back. Has the performance improved? Is it at the level of VS Code?

The one reason I'm still using Atom is because of the remote editing experience with Nuclide + Watchman server-side. No other editor that I've tried comes even close (the connection drops, files get out of sync, new files don't show up, etc, etc) Given the huge number of people who work on remote servers, I find it surprising that proper solutions are still so hard to find. A "file system provider API" for VSCode is…

I am curious about your situation that causes you to edit files remotely. I've never had to edit files anywhere but my local file system. Are you developing or is it more of a devops/sysadmin kind of role?

Re: Atom 1.29

#28
post #9

Honest question: can someone explain why everyone loves emoji these days, especially with regards to 'modern' programming communities such as those around JS and Rust? Is it just a celebration of the fact that we have Unicode support everywhere now?

I find the whole trend very childish and unprofessional. Why? Because emojis don't convey much meaning and borders on child-talk, worst yet, they're very vague and so makes for very poor and unprofessional form of communication.

Re: Atom 1.29

#29
post #23
post #15

Earlier quoted context omitted.

The one reason I'm still using Atom is because of the remote editing experience with Nuclide + Watchman server-side. No other editor that I've tried comes even close (the connection drops, files get out of sync, new files don't show up, etc, etc) Given the huge number of people who work on remote servers, I find it surprising that proper solutions are still so hard to find. A "file system provider API" for VSCode is…

We just use Vim or Emacs over SSH in such cases, or if the connection is good enough over X/RDP.

With Emacs you use it locally and edit via tramp.

Re: Atom 1.29

#30
post #17

Will Atom and Visual Studio Code merge into one project now that Microsoft bought GitHub? Or at least stop sharing extensions? I would vote yes! I would love to see better GitHub integration in VS Code.

The "future CEO of GitHub" said they will continue to develop and support both VSCode and Atom: https://www.reddit.com/r/AMA/comments/8pc8mf/im_nat_friedman... HN discussion here: https://news.ycombinator.com/item?id=17258114

I just really hope they continue with this experiment: https://github.com/atom/xray.

It's reducing Electrons job to the view / plugin layer and have most processing done in a Rust backend.

Post reply on HN