3 ms·

> Did they try to work with the team at Microsoft to improve VS Code before forking it? As an open source project maintainer, I don't think it's necessary or e

by zabil 7y ago

> Did they try to work with the team at Microsoft to improve VS Code before forking it? As an open source project maintainer, I don't think it's necessary or easy to do that. Project teams and maintainers have different goals and sometimes it's much easier to fork and evolve without stepping on each other's toes. I'd even say that's the strength of open sourcing software under the right license.

moron4hire 7y ago
In the FOSS world, forking is traditionally considered a hostile action. GitHub normalized the name of the action "fork", but it's not the same thing. GitHub forks are part of the plumbing of their Pull Request metaphor and are not true forks. As long as you're submitting upstream and pulling down, you haven't "forked" the tree.
- gowld 7y ago
  "fork is hostile" is a myth perpetuated by little Napoleons who want to to control how users use their software.
  - fourthark 7y ago
    It really depends on the situation. There are both friendly and hostile forks.
hexa00 7y ago
Note this is Not a fork, it's a from scratch implementation that is compatible with the extensions of VSCode, not a vscode fork.
- MikusR 7y ago
  If by "from scratch" you mean, taking Microsofts MIT licenced Monaco editor and adding some stuff around it, then yes it's not a fork.
- nvrspyx 7y ago
  Yeah, I'm sure they just happened to make a one-to-one exact recreation of the VS Code UI as well, huh?