I don’t understand why Microsoft hasn’t pulled the GitHub integration into VS Code. It seems like it would be in their best interest given that they own both now.
Atom 1.36
61–70 of 75 posts
Re: Atom 1.36
#62Earlier quoted context omitted.
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?
I think you'll find that it's easier to do in Atom. However - Atom's API is also probably easier to shoot yourself in the foot with.
Maybe try getting started on both, and see which one is easier or more comfortable?
Re: Atom 1.36
#63Atom is still being developed?
Re: Atom 1.36
#64Prediction: 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.
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…
> and binary spyware in it "phones home" to its users' masters in Redmond
Not a problem, https://vscodium.com/
Re: Atom 1.36
#65Prediction: 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…
> VS Code has had excellent git integration for a long time
I don't agree. Last time I've checked vscode fails un some rather basic requirements, as for example vscode's file renaming functionality is entirely oblivious to Git which causes unnecessary problems to the user.
Re: Atom 1.36
#66Earlier 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…
I got it, but I'm not sure I'm ready :-) Thanks for sharing!
Re: Atom 1.36
#67Earlier 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…
Simple is not always better. Especially with plugins you often also want a certain level of quality, organisation and control. I don't know much about the difference between Atom and VS Code on that front in detail, but compared to the more customizable editors (Emacs, vim, Sublime) I was always impressed with the quality of VS Codes plugin-system. While Atom made for a more messy impression, and it was at last the reason why I started to use VS Code more as a side-editor, instead of Atom.
Re: Atom 1.36
#68To anyone who is following Atom closely, 1. What happened to Xray? The Next Generation of Atom that was suppose to fix all the performance problem of Atom. 2. Is Atom as fast as VS Code now?
1. https://github.com/atom/xray/graphs/contributors
Seems it's been not much done since february.
Re: Atom 1.36
#69To anyone who is following Atom closely, 1. What happened to Xray? The Next Generation of Atom that was suppose to fix all the performance problem of Atom. 2. Is Atom as fast as VS Code now?
1. I haven't heard anything about it recently but that doesn't mean work isn't continuing on it. Xray wasn't supposed to "fix" anything really, it was a fairly extreme experiment to see if it would be worth going down that path. 2. No, and it's not trying to be, as "speed" isn't their top priority, extensibility is. That being said, the days of opening a 5mb file and the editor getting brought to its knees are largel…
> in Atom extensions are EVERYTHING and can do ANYTHING).
So Atom is the emacs of Webstack-World?
Re: Atom 1.36
#70To anyone who is following Atom closely, 1. What happened to Xray? The Next Generation of Atom that was suppose to fix all the performance problem of Atom. 2. Is Atom as fast as VS Code now?
1. I haven't heard anything about it recently but that doesn't mean work isn't continuing on it. Xray wasn't supposed to "fix" anything really, it was a fairly extreme experiment to see if it would be worth going down that path. 2. No, and it's not trying to be, as "speed" isn't their top priority, extensibility is. That being said, the days of opening a 5mb file and the editor getting brought to its knees are largel…
Strange they are not focusing on Speed.
The primary reason VS Code took over Atom was because of Speed. It shows what is possible with Electron. Not that it is anywhere near the speed of Sublime Text, but it was good enough for most and at least bearable to me. Compared to Atom, all the feedback ( on most Internet forum at least ) are performance related.