4 ms·
When you couple services together, you decrease the potential user base. For example, Github issues are underpowered for many people. But at least you can igno
by neilk 8y ago
When you couple services together, you decrease the potential user base.
For example, Github issues are underpowered for many people. But at least you can ignore them and use your own service.
Many source control systems tried to offer all-in-one platforms but it’s never worked so far. In fact, we don’t even do PRs the way the authors of git intended.
For integrations, it might be better to settle on a configuration file format and maybe some conventions. Maybe that could be checked into your repo.
But then you need fine-grained control over who can modify that, and encryption to keep passwords secret, and those aren’t standard features of source control either.
Maybe we could come up with conventions that were great for hobbyists and the enterprise. But open source communities and standards committees are really bad at that, compared to just leaving it the marketplace.
- twblalock 8y agoPlus, even if Git did have all of the features people want today, people will continue to think of new features that are not supported by Git and need to be implemented outside of it.