3 ms·
The pitch simply wasn’t true. Data was not destroyed and was restored hours later.
by MrDarcy 3y ago
The pitch simply wasn’t true. Data was not destroyed and was restored hours later.
- swells34 3y agoIt's a pitch. The story has obviously been embellished and polished and condensed, ready public consumption. Being pedantic against it is not productive.
- yjftsjthsd-h 3y agoIf the pitch is dishonest, why would I ever trust them with something as vital as my VCS? (And yes, "embellished" means dishonest)
- spiderice 3y agoThat's a creative way to defend a dishonest pitch
- MrDarcy 3y agoPolitely disagree. It’s productive because hopefully future teams who launch on HN ask each other, “Is what we’re saying true?” during all those polishing and condensing sessions. If they don’t, the risk is crossing a line that damages the reputation of the team and undermines months if not years of hard work.
- water-your-self 3y agoThis is not a pedantic criticism.
- lowbloodsugar 3y agoFor many of us, the story rings true. We have ourselves had horror stories that we did manage to recover from after a few hours of fearfully googling, and we know of other, less capable friends and colleagues who were unable to recover the data and who just accepted the loss.
- TexasMick 3y agoIt's kinda crazy argument, I think data loss is way more likely with a centralised system than a decentralised system.
- lowbloodsugar 3y agoYou think Microsoft losing GitHub repos is more likely than poor bastards trying to make sense of the git command line? You think these guys are going to do a worse job with their centralized service?
- TexasMick 3y agoPeople have lost data on GitHub from repositories being copyright striked for example. At least with git, every developer has a copy of the full history so full data loss is impossible really. What happens if this company folds? You're left with some proprietary repo that you suddenly have to workout how to self host. It just doesn't make sense when compared to just learning git which is definitely the most fruitful thing a developer could learn at the start of their career.