3 ms·

>MO, the problem with GitHub is the community. For some reason the Ruby community rubs me the wrong way While I get that same feel from the rubbings from some

by gte910h 16y ago

>MO, the problem with GitHub is the community. For some reason the Ruby community rubs me the wrong way While I get that same feel from the rubbings from some ruby folk, (I'm a C/python/Objective C guy mainly), I don't honestly feel their rubbings in relation to github at all. I mean, it's source control, what does it have to do with the language you put into it? Are you rejecting git too because rubyiests happen to use grabbed onto Linus Torvald's version of Hg?

kenjackson 16y ago
While I get that same feel from the rubbings from some ruby folk, (I'm a C/python/Objective C guy mainly), I don't honestly feel their rubbings in relation to github at all. I mean, it's source control, what does it have to do with the language you put into it? As the author of the original blog entry stated, feature-wise Git is similar to many other source control systems, "The issue wasn't the technology. Mercurial and Git are pretty much at feature parity (as is Bazaar)." He goes on to say that the differentiator is the community. If the source control system isn't technologically superior to other competing technologies, and the community is the differentiating factor, but the community is one that I'm not extremely enamored with, wouldn't I be wise to stay away? Maybe what you're saying is that in fact the community is not that important with repect to GitHub. It's a web front end for source control and it's really good, period. In that case, maybe it's worth another look. Although again, pretty much the only people I hear talking about GitHub are Ruby folks, and most of what they talk about is how GitHub is great because of the Ruby community.
- gte910h 16y ago
  I didn't even catch that in the original article which I did read. Your comment makes much more sense. Having used Hg and git, I do not feel they're equivalent. I feel Hg is quite a bit more friendly to new folks, however git is considerably more powerful feeling to moderately good folks. I'm honestly a little sad python people are so enamored with Hg :o( Honestly, the "Your repo can be marked public or private" thing gives me the willies. I prefer offerings which don't support public status, so you never accidentally dump your codebase onto the internet. But if you are doing something open source, it fantastic.

by gte910h 16y ago

kenjackson 16y ago

While I get that same feel from the rubbings from some ruby folk, (I'm a C/python/Objective C guy mainly), I don't honestly feel their rubbings in relation to github at all. I mean, it's source control, what does it have to do with the language you put into it? As the author of the original blog entry stated, feature-wise Git is similar to many other source control systems, "The issue wasn't the technology. Mercurial and Git are pretty much at feature parity (as is Bazaar)." He goes on to say that the differentiator is the community. If the source control system isn't technologically superior to other competing technologies, and the community is the differentiating factor, but the community is one that I'm not extremely enamored with, wouldn't I be wise to stay away? Maybe what you're saying is that in fact the community is not that important with repect to GitHub. It's a web front end for source control and it's really good, period. In that case, maybe it's worth another look. Although again, pretty much the only people I hear talking about GitHub are Ruby folks, and most of what they talk about is how GitHub is great because of the Ruby community.

gte910h 16y ago
I didn't even catch that in the original article which I did read. Your comment makes much more sense. Having used Hg and git, I do not feel they're equivalent. I feel Hg is quite a bit more friendly to new folks, however git is considerably more powerful feeling to moderately good folks. I'm honestly a little sad python people are so enamored with Hg :o( Honestly, the "Your repo can be marked public or private" thing gives me the willies. I prefer offerings which don't support public status, so you never accidentally dump your codebase onto the internet. But if you are doing something open source, it fantastic.