5 ms·

My IDE allows me to easily annotate each line with author and commit message. Invaluable information.

by edejong 8y ago

catmanjan 8y ago
What if someone changes the line? You lose the useful commit message
- masklinn 8y ago
  VCS UI generally have a way to re-annotate the previous revision (even "git gui" does), if the code was changed since the original commit but the change is not what I'm concerned with. More often than not, you only need a few jumps before reaching the change you're interested in.
maccard 8y ago
The file I have open right now is 1500 lines with probably 400 revisions across numerous branches. Many of those revisions are going to be integrates across branches. How is my IDE supposed to know which of those revisions are the ones that I care about? And more to the point, how is it supposed to do that _quickly_ ?
- masklinn 8y ago
  > The file I have open right now is 1500 lines with probably 400 revisions across numerous branches. I have a 1500LOC files with 1100 revisions right here, "git annotate" processes it in 2.356 seconds on a 2010 MBP, and PyCharm barely takes any longer (maybe 3s). > How is my IDE supposed to know which of those revisions are the ones that I care about? It does not care, it gives you a baseline annotation and if that's too recent you drill down into previous annotations.
  - maccard 8y ago
    > (maybe 3s) > you drill down into previous annotations No thanks. I’d rather have a comment inline in the code than add 3 seconds per file, and still have to go searching through the history.
  - glenneroo 8y ago
    What happens when your version control dies? Of course it shouldn't happen, but we all know about Murphy's Law. Or as I've encountered on multiple occasions: your IT team is struggling to figure out why your network/version control/etc are extremely slow... 3 second queries are now taking 60 seconds... we will be rebooting servers a few times... and restoring backups... hopefully things are working better tomorrow! Or what happens when you migrate to another versioning system? Where I was working migrated from MS SourceSafe years ago and a lot of comment history was lost in the conversion and apparently it wasn't worth the time/money to figure out why only half the comments made it over. I'm sure there are more scenarios. The point is: comments in plain-text source files can be invaluable.
    - maccard 8y ago
      > your IT team is struggling to figure out why your network/version control/etc are extremely slow Which is exacerbated by everyone's IDE now querying VC for every file!
      - mywittyname 8y ago
        Git, the VCS in question, is capable of cloning an entire repository locally. So this shouldn't be an issue.
        maccard 8y ago
        But not everyone is using git! (I.e. me)
        glenneroo 8y ago
        Me neither :/

My IDE allows me to easily annotate each line with author and commit message. Invaluable information.

catmanjan 8y ago

What if someone changes the line? You lose the useful commit message

masklinn 8y ago
VCS UI generally have a way to re-annotate the previous revision (even "git gui" does), if the code was changed since the original commit but the change is not what I'm concerned with. More often than not, you only need a few jumps before reaching the change you're interested in.

maccard 8y ago

The file I have open right now is 1500 lines with probably 400 revisions across numerous branches. Many of those revisions are going to be integrates across branches. How is my IDE supposed to know which of those revisions are the ones that I care about? And more to the point, how is it supposed to do that _quickly_ ?

masklinn 8y ago
> The file I have open right now is 1500 lines with probably 400 revisions across numerous branches. I have a 1500LOC files with 1100 revisions right here, "git annotate" processes it in 2.356 seconds on a 2010 MBP, and PyCharm barely takes any longer (maybe 3s). > How is my IDE supposed to know which of those revisions are the ones that I care about? It does not care, it gives you a baseline annotation and if that's too recent you drill down into previous annotations.
- maccard 8y ago
  > (maybe 3s) > you drill down into previous annotations No thanks. I’d rather have a comment inline in the code than add 3 seconds per file, and still have to go searching through the history.
- glenneroo 8y ago
  What happens when your version control dies? Of course it shouldn't happen, but we all know about Murphy's Law. Or as I've encountered on multiple occasions: your IT team is struggling to figure out why your network/version control/etc are extremely slow... 3 second queries are now taking 60 seconds... we will be rebooting servers a few times... and restoring backups... hopefully things are working better tomorrow! Or what happens when you migrate to another versioning system? Where I was working migrated from MS SourceSafe years ago and a lot of comment history was lost in the conversion and apparently it wasn't worth the time/money to figure out why only half the comments made it over. I'm sure there are more scenarios. The point is: comments in plain-text source files can be invaluable.
  - maccard 8y ago
    > your IT team is struggling to figure out why your network/version control/etc are extremely slow Which is exacerbated by everyone's IDE now querying VC for every file!
    - mywittyname 8y ago
      Git, the VCS in question, is capable of cloning an entire repository locally. So this shouldn't be an issue.
      - maccard 8y ago
        But not everyone is using git! (I.e. me)
        glenneroo 8y ago
        Me neither :/