3 ms·

> 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 point

> 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.