• 0 Posts
Joined 1Y ago
Cake day: Jun 28, 2020


I think in most cases you want the dependencies between commits that darcs removes. For instance, let’s say you have three patches:

  1. Create hello.sh with echo Hello World
  2. Create lib.sh with hello() {echo Hello World}
  3. Edit hello.sh to source lib.sh; hello

Of course, in this case it would be easy to manually specify the dependency (3 depends on 2) and unlike git 2 wouldn’t have to depend on 1. But for a larger project I’m imagining always having to look at the current path set to figure out dependencies and the git model of “every commit depends on the patch before” seems better for large codebases.

But I could be wrong. I’d be curious to see what a large darcs repo looks like.

I remember when I first discovered bitcoin it was below $100 (USD). I mined a few dollar worth (which would be a few hundred dollars now) and then uninstalled it, since it would’ve taken too long on my crappy PC and moved on. Pretty sure I deleted the private keys at that point too. When I uninstalled it I thought, “this is a really cool idea, but probably won’t go anywhere, so it’s not worth my time.” This is why I invest in index funds and don’t pick stocks.