undefined | Better HN

0 pointsdavesque10y ago0 comments

Agreed about Bitbucket. I've used it for a long time and haven't found it to be substantively different from GitHub in either functionality or reliability. The major downside, as I see it, is that it's just not as popular.

0 comments

6 comments · 3 top-level

chrisan10y ago· 2 in thread

> The major downside, as I see it, is that it's just not as popular.

Has anyone really thought of this? Do people just happen on to a github project because "it is on github" or because someone linked their work and people liked it and wanted to contribute?

Would React, D3, Rails, Bootstrap etc not get what they do now simply because "oh I don't have a bitbucket account, I'm not going to bother"

To me at least this kind of argument (I hear a lot of, nothing personal davesque!) is along the lines of "everybody is on MySpace"

tomjakubowski10y ago

> Has anyone really thought of this? Do people just happen on to a github project because "it is on github" or because someone linked their work and people liked it and wanted to contribute?

I happen to have a BitBucket account, so I can't speak directly to your point, but I'm less likely to file issues on a project if I have to register a new account with their bug tracker to do so. I imagine the same would apply to a project hosted on BitBucket if I had a GitHub account but not one on BitBucket.

davesqueOP10y ago

Right, and, just to be clear, I actually wasn't trying to suggest that this downside is really justified (and I think you understand this). Mind share is important, however.

StevePerkins10y ago· 1 in thread

Popularity is certainly important for open source stuff, and personal code samples that you put online for "resume" purposes. Hell, for that use case you might as well be posting your code on LinkedIn.

But for the use cases in which people actually pay money (i.e. private repos that you don't WANT outsiders to access), then how is lack of popular visibility a downside?

davesqueOP10y ago

For open source I suppose, since GitHub being so popular makes it easier for people to contribute to your project. Still, though, the only obstacles in using Bitbucket for those purposes (that I know of) are that you need to sign up for a Bitbucket account and learn how to make pull requests. As far as resume code goes, I wouldn't trust an employer who thinks having code samples hosted on Bitbucket is a mark against you. There's just nothing different between GitHub and Bitbucket in that case. Or is there some other issue I'm not aware of?

bybjorn10y ago

bitbucket for private repos, github for public. No downside there :-)

j / k navigate · click thread line to collapse

0 comments

6 comments · 3 top-level

chrisan10y ago· 2 in thread

> The major downside, as I see it, is that it's just not as popular.

Has anyone really thought of this? Do people just happen on to a github project because "it is on github" or because someone linked their work and people liked it and wanted to contribute?

Would React, D3, Rails, Bootstrap etc not get what they do now simply because "oh I don't have a bitbucket account, I'm not going to bother"

To me at least this kind of argument (I hear a lot of, nothing personal davesque!) is along the lines of "everybody is on MySpace"

tomjakubowski10y ago

> Has anyone really thought of this? Do people just happen on to a github project because "it is on github" or because someone linked their work and people liked it and wanted to contribute?

davesqueOP10y ago

Right, and, just to be clear, I actually wasn't trying to suggest that this downside is really justified (and I think you understand this). Mind share is important, however.

StevePerkins10y ago· 1 in thread

But for the use cases in which people actually pay money (i.e. private repos that you don't WANT outsiders to access), then how is lack of popular visibility a downside?

davesqueOP10y ago

bybjorn10y ago

bitbucket for private repos, github for public. No downside there :-)

j / k navigate · click thread line to collapse