4 ms·

That is the scariest script I have ever seen in my life. It makes me believe there is a real existential problem with git as a product.

by jariel 7y ago

cryptonector 7y ago
I wrote it on the spot. The actual script is here: https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee6509c3526297 https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...
foobarian 7y ago
The nice thing is that git is serverless, so you can clone a throwaway repo and run this sort of risky thing safely. It makes what's impossible in SVN possible, though maybe not easy.
- jariel 7y ago
  ... unless someone scripts pushing and pulling. ... unless changes were not already pushed and therefore 'saved'. Git is inherently dangerous and overly complex - such a script shouldn't ever have to exist for so many reasons.
cryptonector 7y ago
Oh get off your high horse. Git started as a collection of small programs and shell scripts, and as time went by more of those scripts became programs.
- jariel 7y ago
  How it came to be is basically irrelevant when determining how materially useful it is, given all the bizarre artifacts of git. Nobody really seems to really have mastered it, most people seem to grasp only a subset, and there are so many potential pitfalls. It's a very powerful, raw technology that hasn't been properly productized, or rather, 'it works how Linus wants it to for his reasons' and everyone else just gets dragged along.
  - cryptonector 7y ago
    > Nobody really seems to really have mastered it You can speak for yourself. Don't speak for me or my colleagues.
    - jariel 7y ago
      I'll bet $1000 that zero of your colleagues have truly mastered git. I've watched countless times as employee X did something wrong, the so-called 'git experts' gaggle around them and spend quite a bit of time trying to 'fix' the situation, all with varying approaches that their peer gitters barely understood. All blissfully unaware that their 'intelligence signalling' is woefully misplaced as such situations should not arrive in the first place, and if they did, they should be easily remedied. Moreover, it doesn't matter that 'a few people' have very strong Git skills, the point is - the vast majority don't and there should absolutely be no need for them to - the problems most developers face re: code management are simply not complex enough to warrant the power of the tool. The failure to understand this among so many glib gitters is basically existentially problematic. The inability to grasp the difference between 'raw power' and usability, complexity and the resulting costs ... is the real problem.

That is the scariest script I have ever seen in my life. It makes me believe there is a real existential problem with git as a product.

by jariel 7y ago

That is the scariest script I have ever seen in my life. It makes me believe there is a real existential problem with git as a product.

cryptonector 7y ago

I wrote it on the spot. The actual script is here: https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee6509c3526297 https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...

foobarian 7y ago

The nice thing is that git is serverless, so you can clone a throwaway repo and run this sort of risky thing safely. It makes what's impossible in SVN possible, though maybe not easy.

jariel 7y ago
... unless someone scripts pushing and pulling. ... unless changes were not already pushed and therefore 'saved'. Git is inherently dangerous and overly complex - such a script shouldn't ever have to exist for so many reasons.

cryptonector 7y ago

Oh get off your high horse. Git started as a collection of small programs and shell scripts, and as time went by more of those scripts became programs.

jariel 7y ago
How it came to be is basically irrelevant when determining how materially useful it is, given all the bizarre artifacts of git. Nobody really seems to really have mastered it, most people seem to grasp only a subset, and there are so many potential pitfalls. It's a very powerful, raw technology that hasn't been properly productized, or rather, 'it works how Linus wants it to for his reasons' and everyone else just gets dragged along.
- cryptonector 7y ago
  > Nobody really seems to really have mastered it You can speak for yourself. Don't speak for me or my colleagues.
  - jariel 7y ago
    I'll bet $1000 that zero of your colleagues have truly mastered git. I've watched countless times as employee X did something wrong, the so-called 'git experts' gaggle around them and spend quite a bit of time trying to 'fix' the situation, all with varying approaches that their peer gitters barely understood. All blissfully unaware that their 'intelligence signalling' is woefully misplaced as such situations should not arrive in the first place, and if they did, they should be easily remedied. Moreover, it doesn't matter that 'a few people' have very strong Git skills, the point is - the vast majority don't and there should absolutely be no need for them to - the problems most developers face re: code management are simply not complex enough to warrant the power of the tool. The failure to understand this among so many glib gitters is basically existentially problematic. The inability to grasp the difference between 'raw power' and usability, complexity and the resulting costs ... is the real problem.