Hacker News new | past | comments | ask | show | jobs | submit login

Github is the perfect example. Very "pro-geek". But can you imagine if they had appealed to only people who are comfortable with the command-line and with no GUI's? Github is in many ways just a nice GUI and good documentation on top of git, making it more accessible for the average programmer.

And does anyone honestly think the world would be better if git was less widespread?




Perhaps I'm just strange but I wouldn't pay for GitHub and I am the reason that we went with GitLab at $DAY_JOB since its my responsibility to maintain everything Git.

The majority of my coworkers are GitHub's target audience [programmers that do not really want to truly understand how Git works] and they have no active desire to use GitHub. I'm literally the only person that works here with a GitHub account which I barely use because I run a private instance of GitLab instead.

So, while it is a perfect 'mainstream' example, in your eyes...it is also a prime example that there is a significant market that wouldn't use GitHub professionally.


I don't really agree with this characterization of GitHub's target audience. After spending the last 18 months working with a distributed team of ~40 engineers and ~20 bizdev/salesfolk I cannot imagine a suitable replacement for GitHub when it comes to organizing the information surrounding our workflow. I am now in a 2-man startup and it is indispensable for its ticketing and communication features, not to mention helping me figure out when I am most productive. Also, do you realize how great it is for non-coders to "get" GitHub and start using it for critical documents? Iterating through some legal agreements is much clearer when your lawyer/partner now understands what a repo is and how to revert to a previous commit.


That's fine, my comment/explanation could have been clearer.

I was trying to explain that there is two markets for backups/Tarsnap and trying to shoe-horn it into the GitHub comparison led to confusion.

GitHub sounds like it is a SPoF for you is the only reason I'm adding this part of the comment:

If you can't 'imagine' a suitable replacement, I'd try GitLab. They are similar enough I think you'll be surprised how easy it is to replace GitHub in your workflow.

I'm not suggesting you actually replace GitHub, I'm just suggesting you expand your options so you have a backup plan in case GitHub disappears one day.


And there are many enterprises that pay for GitHub Accounts or Private instances of GitHub Software on prem...

Why... Same reason companies pick any other software... Same reason companies pick RHEL over Cent... etc

Support, Security, and outsourced management

If your team has the time to manage your GitLab installation, update it, fix it if/when it breaks, etc. Great. Other organization choose to outsource that to GitLab...

Same thing here with backups... People that want to roll their own inhouse solution would not be TarSnaps target.


Fyi, GitLab and GitHub both provide similar services. One is open source, one is not.

You can buy on premise support from GitLab or GitHub for their respective products.

So, it isn't rolling your own...or even being on your own [unless you choose to be].

The confusion is probably my fault, I'm not the clearest of posters.


Just out of interest, why do you think GitHub's target audience are developers who don't want to truly understand git?


Git is as easy to use as scp or rsync from the commandline for most common tasks. So is Tarsnap.

The Tarsnap -> Patio11's Idea is being approximated as equivalent to Git -> GitHub.

So, in this context, the people I've dealt with that would want Patio11's Idea of Tarsnap are people who don't want to take the effort to understand what they are dealing with.

GitHub has a larger audience that has nothing to do with development. Social features, simplifying things for non-developers, etc. but I do not feel that portion of the 'product' is relevant in this context.

The people I know IRL that prefer a GitHub-type interface over doing things with Git via the command line are the type that need me to fix the issues they run into for them. The fact I'm basically git support for other IT folk leads me to that conclusion.

And frankly, I'm not a Git guru. I'm a very, very average software developer who acts as the sysadmin for Dev at $DAY_JOB.

I fully believe other people have different experiences but I've implemented Git workflows at 2 companies now and I've seen a consistent pattern.

Please do understand, I'm not saying they should or need to learn Git. It is better they focus on the domain expertise they bring to the table [e.g. Web Design, Email Design, Data Science]. I'm just saying it is a different audience than Tarsnap's current one.


I'm one of them. For me it's because I made some token efforts before to understand it, and it seemed far more complicated than source control should be. I have very simple needs, and correspondingly don't really have a desire to learn non simple tools.


And if that works for you, you shouldn't learn it. :)

But I think Tarsnap -> Patio11's Idea is like Git -> GitHub. I think there are two separate audiences there with different needs.


100%. Tarsnap is like GitHub if it were priced by picodollars per byte in the repository blob.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: