4 ms·

> I agree with what it says; however, using Discord is even worse than using GitHub, since GitHub is a git-based service which others I think Github is worse.

by rapnie 3y ago

> I agree with what it says; however, using Discord is even worse than using GitHub, since GitHub is a git-based service which others I think Github is worse. The pervasiveness of this centralized platform leads to a way more insidious form of lock-in. Look at the vast landscape of developer tool vendors who offer some kind of Github integration features out of the box. These aren't even unique selling points, they are expected functionality. Bringing Micosoft Github in a very luxurous position where they can pick'n choose nuggets into their platform to slowly bring more value to their products and services. It is all seemingly open, but you are a frog in boiling water, getting more dependent on the platform. This goes much further than git vs. github. The Github product suite offers real productivity gains, that cover many aspects of the software development lifecycle. And more added all the time. Hyper convenient, click and go. It is their strategic direction to cover ever more of this SDLC and intertwine with other products and services along the way. From that regard git is just the data export format, your data takeout if you decide to leave. And good luck to find comparative services elsewhere.

zzo38computer 3y ago
> Look at the vast landscape of developer tool vendors who offer some kind of Github integration features out of the box. These aren't even unique selling points, they are expected functionality. It is a valid point, but you are not necessarily required to use such tools (I deliberately don't use them, due to these problems). Of course, some people do; as long as they are not mandatory, you could still use the program being made by the project, elsewhere. > From that regard git is just the data export format It is import as well as export. (However, this does not include the issues. The API is documented, but I don't know if any other git-based services support the same JSON format used by GitHub for this purpose.)
- rapnie 3y ago
  > It is a valid point, but you are not necessarily required to use such tools (I deliberately don't use them, due to these problems). Yes, it is very prudent if you are considerate like that, and you mitigate the risks of lock-in that way. But.. > Of course, some people do I would say most people that have their stuff on Github use many of the power features and conveniences they bring without much deliberation on the lock-in aspects, and also use the Github integrations of a range of additional 3rd-party developer tools too. Companies make these choices, often as a no-brainer, since it is a logical choice for what are simply the 'best tools' on the market. And then devs start using those too for their own personal projects.

by rapnie 3y ago

zzo38computer 3y ago

> Look at the vast landscape of developer tool vendors who offer some kind of Github integration features out of the box. These aren't even unique selling points, they are expected functionality. It is a valid point, but you are not necessarily required to use such tools (I deliberately don't use them, due to these problems). Of course, some people do; as long as they are not mandatory, you could still use the program being made by the project, elsewhere. > From that regard git is just the data export format It is import as well as export. (However, this does not include the issues. The API is documented, but I don't know if any other git-based services support the same JSON format used by GitHub for this purpose.)

rapnie 3y ago
> It is a valid point, but you are not necessarily required to use such tools (I deliberately don't use them, due to these problems). Yes, it is very prudent if you are considerate like that, and you mitigate the risks of lock-in that way. But.. > Of course, some people do I would say most people that have their stuff on Github use many of the power features and conveniences they bring without much deliberation on the lock-in aspects, and also use the Github integrations of a range of additional 3rd-party developer tools too. Companies make these choices, often as a no-brainer, since it is a logical choice for what are simply the 'best tools' on the market. And then devs start using those too for their own personal projects.