91–100 of 120 posts
I feel like a lot of their resources are being put towards git integration instead of improving the editor and performance... which are some of the primary reasons people leave for VSCode.
Maybe I'm the odd man out though, since I like to use CLI git directly.
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 don't understand the desire for all the git integration into the editor. I mean, it might make sense because Atom is owned by Github, but why otherwise? I feel like a lot of their resources are being put towards git integration instead of improving the editor and performance... which are some of the primary reasons people leave for VSCode. Maybe I'm the odd man out though, since I like to use CLI git directly.
A good git interface really is a game changer and can speed up your workflow quite a bit, especially if you utilize feature branches/git flow.
I don't understand the desire for all the git integration into the editor. I mean, it might make sense because Atom is owned by Github, but why otherwise? I feel like a lot of their resources are being put towards git integration instead of improving the editor and performance... which are some of the primary reasons people leave for VSCode. Maybe I'm the odd man out though, since I like to use CLI git directly.
But then I figured out that Atom's git integration is actually quite neat and I started using it mostly to do `git add -i` as it makes staging files or parts of files really easy.
I still don't trust it with pushing/pulling, switching branches etc. so I still drop to the command line for those, but the atom git integration is incredibly useful for seeing your changes and committing a particular part of them.
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?
> bare minimum should be maintaining 60 FPS Yours would be a nice world to live in. I've seen IntelliJ and Eclipse both crawl when doing "basic editing tasks". Hell, Vim does it too if your line length is long.
Or even if it is short if you're using LaTeX with syntax highlighting. This even has its own entry in the manual, called tex-slow (http://vimdoc.sourceforge.net/htmldoc/syntax.html#tex-slow).
Earlier quoted context omitted.
With Emacs you use it locally and edit via tramp.
I never heard of tramp, thanks.
Also, the manual is pretty good. It comes with Emacs, of course, or can be read at https://www.gnu.org/software/tramp/
My favorite thing about TRAMP is how well integrated it is. It's not just opening remote files, you can also open shells on remote systems, or do file management with dired (I have a bookmark pointing to dired on a remote system I use frequently, for example.)
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?
Would that the unicode support was indeed ubiquitous. Then you wouldn't need to parse the message for things like ":penguin:", you could just include the appropriate character/icon.
Earlier quoted context omitted.
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.