> why would they create a dependency on an open service (that could disappear at any moment) when they could roll their own?
Because by creating the dependency on an open service and collaborating with them, they help them survive long term and to not disappear at any moment.
Yes, it's nice that "it just works" but sometimes the easiest way of doing something doesn't mean it's the right way. Especially when it comes to hard things like "How do we ensure open source developers can get paid?"
Having worked with human beings before, I would say that it is considerably easier and more predictable if you just do some things yourself.
Working with folks outside of your employ (even if you pay them good money to do the work) will fail you far more often than working with one or more of your own employees.
I can't blame GitHub for doing this completely in-house.
Sure, the easy way is easier. But more often than not, the easiest way is not the best way for the entire ecosystem.
Rather than saying "How can we get money moving around on our platform as soon as possible?" they should have asked "How can we make open source work sustainable?".
But who can blame them really, it's a for-profit and closed source company on every level.
Because by creating the dependency on an open service and collaborating with them, they help them survive long term and to not disappear at any moment.
Yes, it's nice that "it just works" but sometimes the easiest way of doing something doesn't mean it's the right way. Especially when it comes to hard things like "How do we ensure open source developers can get paid?"