4 ms·
Do for crypto what GitHub did for git? You mean take something that's already well-distributed and introduce a central SPOF for many people's workflows? Sure,
by notacoward 13y ago
Do for crypto what GitHub did for git? You mean take something that's already well-distributed and introduce a central SPOF for many people's workflows? Sure, they can do that.
- dasil003 13y agoI think you should look at the adoption curve of git before and after GitHub to temper your snark. edit: and you think your previous account got hellbanned because of "disagreement with the herd". Open your eyes and take a look at yourself.
- notacoward 13y agoLikewise, I'm sure. Did your personal attack, grounded in defense of the conventional view, contribute to the discussion?
- dasil003 13y agoYou're a hilarious guy. Don't dish it out if you can't take it.
- CJefferson 13y agoWhere is this adoption curve for me to look at?
- FiloSottile 13y agoAnd by making it more accessible bring it to a number of users that before simply went (without VCS or sharing|unencrypted)? Sure, I hope they do that.
- notacoward 13y agoYep, that's a good thing too, but there seemed to be plenty of people (including the OP) already looking at it from that perspective. There are benefits, and drawbacks. Both need to be considered.
- Tobani 13y agoI'm not sure I follow where THEY introduced the SPOF. Having a central repo is convenient for many people's workflow so there would probably be a SPOF (In that sense) for the people using github anyway. The difference becomes would you have a team dedicated to maintaining your git repos if you didn't use github? Is your qualm with the fact that many people share the same SPOF? Sure Github has their outages from time to time, but it doesn't prevent me from sharing code. Git is still distributed. It might be inconvenient when it is down, but its not a full-out failure of the system. Escalator temporarily stairs. Sorry for the convenience.
- notacoward 13y agoThe problem is that a lot of people who use GitHub because it's convenient stop using git as a distributed VCS. They don't have a backup when it goes down, and their productivity is significantly impacted during those service interruptions. In a way you're right that it's not GitHub's fault, except to the extent that such interruptions seem more common than one might expect. This is often what happens when we use web services to make something more convenient. What's important is that people should consider this downside along with the upside of greater convenience and operational simplicity. Often they'll choose to forward anyway. More power to them and their providers. OTOH, some would be better served by sticking with a truly distributed alternative.
- sanderjd 13y ago> don't have a backup when it goes down What about the one or (more often) many local versions of the repository on peoples' computers? You can't stop using git as a distributed VCS. Everyone always has a full copy.
- notacoward 13y agoYes, you can do local/personal work, but if GitHub was your only way to share that work with others, or the only place you had your reviews and bug reports, then all of that comes to a halt during the outage. IMX many GitHub users have forgotten (or never knew) how to email or apply a patch so work can go on. They just get totally blocked. As I said in another sub-thread, that's not really GitHub's fault but it's something adopters should consider and (probably) seek to ameliorate.
- deleted 13y ago[deleted]