4 ms·

Tbh, I like this move. I hope they will merge Atom with VS Code and shutdown VSTS in favor for GitHub.

by madspindel 8y ago

mikece 8y ago
Atom and VS Code are both built on Electron. No need to kill Atom as it and VS Code are built for different purposes.
- carlosdp 8y ago
  What different purposes? They're both text editors / lightweight IDEs focusing on plugin extensibility built on top of Electron. They're literally the same thing.
  - Klathmon 8y ago
    And there are many who would say a sedan and a crossover are basically the same thing, but the devil is in the details. Atom is extensible to a fault. A plugin can do just about everything and anything. FFS tabs are actually a plugin! While that means that performance will suffer, many (myself included) use Atom because of that insane freedom that plugins have to do what they need to do. VSCode on the other hand is much more "if you want to do X, use this API". It's much more controlled, much more opinionated about how things "should" be done using VSCode as a platform. From 30,000 ft, they are the same. But their goals and details differ, and I always prefer more choice rather than less.
    - deleted 8y ago
      [deleted]
- deleted 8y ago
  [deleted]
- madeofpalk 8y ago
  I use neither, and I can see that the two take fairly different approaches, but why would you say they're build for different purposes. I don't think it's clear why a single org (though very far apart) has two approaches for a code text editor.
- 013a 8y ago
  Atom has a whole team under Github. If they're both run by Microsoft, that seems like a clear cost-cutting measure; why develop two vastly similar electron-based code editors when you could just move that team + all of the interesting tech into VSCode?
esturk 8y ago
Why do you hope for this outcome?
- hs86 8y ago
  Probably less redundant work and overall a better editor/IDE?
Zekio 8y ago
I wonder if they will merge VSTS or shutdown VSTS, or maybe just add CI and CD from VSTS to github
ezekg 8y ago
I used to be a big fan of Atom in the beginning, but there’s nothing Atom does that VS Code does not do better. I wouldn’t see a purpose in merging the two, but I could see them killing Atom.
EnderMB 8y ago
I agree on the VSTS front, but a lot of people use Atom and I can see many of them being put off by being forced onto VS Code. Lately, based on comments made while promoting .NET Core, it sounds like Microsoft don't want to consolidate tooling, so it wouldn't surprise me to see Atom and VS Code co-exist as entirely separate entities/teams.
the_trapper 8y ago
I'm also optimistic they'll revamp GitHub's pricing structure. Their current price of $7 a month is absolutely absurd for individual developers. I can get a pretty decent VPS for $2 a month cheaper. Considering that most of their competitors give small teams free private repos, their price should be half of that. I understand that they have a lot of open source projects to subsidize and all, but I highly doubt a lot of individual developers are biting at that price.
- gkya 8y ago
  I don't understand why a solo dev needs to host his private repos somewhere. You can just keep it on your machine, and have it backed up with the rest of your data. And given git is distributed, you should be able to work with teams w/o requiring Github.
  - the_trapper 8y ago
    It's a convenience thing for me. As a hobbyist solo dev it'd be nice to have a place to work on code across different devices in private and then open it up when I feel the code is mature enough and the time is right to put it out there under an open source license. Right now I use VSTS for private repos, but it'd be nice to be on GitHub were the vast majority of open source projects are hosted.
  - ctjj 8y ago
    I can only speak for myself, but I like hosting private repos on GitHub because I like using issues & milestones to track my progress
  - demosito666 8y ago
    Especially when you have free bitbucket for that purpose.
  - matthewmacleod 8y ago
    This completely misses the forest for the trees. I currently pay for GitHub, personally. This has the following benefits: - Easy to collaborate with other people if I want to invite them to my projects. - Web-based code hosting, meaning I can access my code from anywhere regardless of whether I have access to my own machine or not. - A web interface! This is quite useful for browsing code or sharing particular snippets with others. - Integration with third-party tools. Almost literally every code-related service that offers integration will integrate with GitHub – things like CI servers etc. for example. This means basically zero-effort setup for many other tools. The cost to me is basically a rounding error, and the utility is great.
freeone3000 8y ago
VSTS does a lot of things that GitHub does not. VSTS takes the workflow roles of Jenkins, GitHub, Jira, and has a few additional features that I don't know what open-source equivilant exists for (staged production, push to cloud - maybe done as Jenkins plugins?). It's highly unlikely VSTS will be shut down, especially in favor of a project which does very few things that VSTS does.
alkonaut 8y ago
If they shut down vsts they would have to make github have vsts’ level of issue management, ci/cd, test management, ... I think most people who use github would NOT want that.

Tbh, I like this move. I hope they will merge Atom with VS Code and shutdown VSTS in favor for GitHub.

mikece 8y ago

Atom and VS Code are both built on Electron. No need to kill Atom as it and VS Code are built for different purposes.

carlosdp 8y ago
What different purposes? They're both text editors / lightweight IDEs focusing on plugin extensibility built on top of Electron. They're literally the same thing.
- Klathmon 8y ago
  And there are many who would say a sedan and a crossover are basically the same thing, but the devil is in the details. Atom is extensible to a fault. A plugin can do just about everything and anything. FFS tabs are actually a plugin! While that means that performance will suffer, many (myself included) use Atom because of that insane freedom that plugins have to do what they need to do. VSCode on the other hand is much more "if you want to do X, use this API". It's much more controlled, much more opinionated about how things "should" be done using VSCode as a platform. From 30,000 ft, they are the same. But their goals and details differ, and I always prefer more choice rather than less.
  - deleted 8y ago
    [deleted]
deleted 8y ago
[deleted]
madeofpalk 8y ago
I use neither, and I can see that the two take fairly different approaches, but why would you say they're build for different purposes. I don't think it's clear why a single org (though very far apart) has two approaches for a code text editor.
013a 8y ago
Atom has a whole team under Github. If they're both run by Microsoft, that seems like a clear cost-cutting measure; why develop two vastly similar electron-based code editors when you could just move that team + all of the interesting tech into VSCode?

esturk 8y ago

Why do you hope for this outcome?

hs86 8y ago
Probably less redundant work and overall a better editor/IDE?

Zekio 8y ago

I wonder if they will merge VSTS or shutdown VSTS, or maybe just add CI and CD from VSTS to github

ezekg 8y ago

I used to be a big fan of Atom in the beginning, but there’s nothing Atom does that VS Code does not do better. I wouldn’t see a purpose in merging the two, but I could see them killing Atom.

EnderMB 8y ago

I agree on the VSTS front, but a lot of people use Atom and I can see many of them being put off by being forced onto VS Code. Lately, based on comments made while promoting .NET Core, it sounds like Microsoft don't want to consolidate tooling, so it wouldn't surprise me to see Atom and VS Code co-exist as entirely separate entities/teams.

the_trapper 8y ago

I'm also optimistic they'll revamp GitHub's pricing structure. Their current price of $7 a month is absolutely absurd for individual developers. I can get a pretty decent VPS for $2 a month cheaper. Considering that most of their competitors give small teams free private repos, their price should be half of that. I understand that they have a lot of open source projects to subsidize and all, but I highly doubt a lot of individual developers are biting at that price.

gkya 8y ago
I don't understand why a solo dev needs to host his private repos somewhere. You can just keep it on your machine, and have it backed up with the rest of your data. And given git is distributed, you should be able to work with teams w/o requiring Github.
- the_trapper 8y ago
  It's a convenience thing for me. As a hobbyist solo dev it'd be nice to have a place to work on code across different devices in private and then open it up when I feel the code is mature enough and the time is right to put it out there under an open source license. Right now I use VSTS for private repos, but it'd be nice to be on GitHub were the vast majority of open source projects are hosted.
- ctjj 8y ago
  I can only speak for myself, but I like hosting private repos on GitHub because I like using issues & milestones to track my progress
- demosito666 8y ago
  Especially when you have free bitbucket for that purpose.
- matthewmacleod 8y ago
  This completely misses the forest for the trees. I currently pay for GitHub, personally. This has the following benefits: - Easy to collaborate with other people if I want to invite them to my projects. - Web-based code hosting, meaning I can access my code from anywhere regardless of whether I have access to my own machine or not. - A web interface! This is quite useful for browsing code or sharing particular snippets with others. - Integration with third-party tools. Almost literally every code-related service that offers integration will integrate with GitHub – things like CI servers etc. for example. This means basically zero-effort setup for many other tools. The cost to me is basically a rounding error, and the utility is great.

freeone3000 8y ago

VSTS does a lot of things that GitHub does not. VSTS takes the workflow roles of Jenkins, GitHub, Jira, and has a few additional features that I don't know what open-source equivilant exists for (staged production, push to cloud - maybe done as Jenkins plugins?). It's highly unlikely VSTS will be shut down, especially in favor of a project which does very few things that VSTS does.

alkonaut 8y ago

If they shut down vsts they would have to make github have vsts’ level of issue management, ci/cd, test management, ... I think most people who use github would NOT want that.