Re: GitHub's “pull request” is proprietary lock-in

[m]

W dniu 03.01.2016 o 05:43, Ben Finney pisze:
> That and other vendor-locked workflow aspects of GitHub makes it a poor
> choice for communities that want to retain the option of control over
> their processes and data.

I'm also afraid that Github will make to git the same thing as Google
did to Jabber/XMPP.

Decade ago, I had plenty of friends on my jabber contacts list. Next,
Google made it's talk compatible with jabber, then my friends slowly
migrated to gtalk, because if they used gmail anyway, then why not use
it also for jabber?

And then Google turned off XMPP support and suddenly I lost ability to
contact with 80% of my friends without having stupid hangouts running,
or without falling back to email (which is not so bad BTW).

The same can be with Github and git. PPL will forget how to use git
without github. When Github will make git-incompatible changes, vast
majority will need/want to follow the changes and eg. will use Gitlabs
propertiary binary.

r. m.