4 ms·
I say "your code belongs to them" in the sense that they are the new LinkedIn-for-developers. The code you put there is your new resume (I kind of disagree wit
by dudul 11y ago
I say "your code belongs to them" in the sense that they are the new LinkedIn-for-developers. The code you put there is your new resume (I kind of disagree with that, but this is a narrative that is very much around). If they ban you you lose access to a big share of the market.
Have fun with your fallacies. (especially the "slippery slope" one has be debunked many times http://www2.law.ucla.edu/volokh/slippery.pdf http://www2.law.ucla.edu/volokh/slippery.pdf) If you don't understand the concept of precedence what do you want me to say? We'll reconvene after their next PR move if you want. I was highlighting the fact that as a private company they can do as they please, yesterday they targeted the 'retard' repo, tomorrow who knows.
"Can you explain how they are posturing?" Really? You are telling me that they're all marketing isn't to represent themselves as the platform for OS? There's nothing wrong with this strategy, but that's what they do.
Funny that you completely ignored my main point: their platform is not open source, it's not hard to see how OS fans may take offense in that.
- dragonwriter 11y ago> I say "your code belongs to them" in the sense that they are the new LinkedIn-for-developers. The code you put there is your new resume (I kind of disagree with that, but this is a narrative that is very much around). If they ban you you lose access to a big share of the market. If you don't have any public share repositories to point to, you lose something. I don't think not being on GitHub specifically is a problem of the same order of magnitude.