2 ms·

I would consider myself pretty knowledgeable and I love going on tangents when setting up projects. I love tinkering and learning. There is no situation in whi

I would consider myself pretty knowledgeable and I love going on tangents when setting up projects. I love tinkering and learning. There is no situation in which I'd want to do all of the above work for every single repository I setup. I have hundreds of repositories that I own on GitHub for things like school assignments and personal projects. If I start a weekend project as you describe then the first 4 hours are going to be setting my repository up. Nobody wants to do this. Just because something is difficult or time consuming doesn't mean that it is good or useful. Doing this once would be a fun learning experience. Doing it more than once is a useless chore.

Dylan16807 4y ago
> There is no situation in which I'd want to do all of the above work for every single repository I setup. What the heck are you talking about? The only work you'd have to do "for every single repository" is the single git command. Getting a server, managing access and discoverability, setting it up for browser access, setting up backups, those are things you would do once. If that's a waste of four hours, valid argument, but it's not a waste of four hundred hours. You're grossly exaggerating the cost. Oh and you didn't mention keeping the server updated but that's probably ten minutes of effort once a month. > Doing this once would be a fun learning experience. Doing it more than once is a useless chore. Then there's no problem.