4 ms·

A new way of doing git diff, leave both versions of the code side by side and cross your eyes.

by a1o 2y ago

louiechristie 2y ago
My thoughts exactly. Could be done with a git diff in a VR headset
- xattt 2y ago
  If you’re already spending the computing effort to create the VR image… /s
justahuman74 2y ago
I sure didn't expect there to be a plausibly work-related angle when I came to this thread
bicx 2y ago
New business idea: git diff, but it uses Mechanical Turk to hire an army of cross-eyed diff spotters.
- waffletower 2y ago
  There is a wonderful stable diffusion prompt here.
- deleted 2y ago
  [deleted]
satvikpendem 2y ago
Somewhat related, but I've been using the Semantic Diff extension in VSCode, works better than standard git diff.
- deleted 2y ago
  [deleted]
deleted 2y ago
[deleted]
tom_ 2y ago
It sounds like you mock, but: you can do this, or near enough, and you can do it already, and it works really well! 0. Pick suitable tool. Firefox works. Notepad++ works. GIMP works. Emacs, not so much, but if you use Emacs, you know that you can fix this 1. Load file A into a tab 2. Load file B into a tab 3. Close all other tabs 4. Hold down the tab switch shortcut key and note the result For images this is actually pretty decent and I've used it a lot. Good for figuring out what the differences actually are when your image-based tests fail, and similarly after making a speculative change. Let your eyes do the difference operation for you. That's what they're there for. For text: you'd be better served by some other kind of tool. But text is just an image with letters in it, so the same principle applies. It does work! (I've previously read a blog post, link to which I of course now can't find, about how old-style Photoshop undo was designed with this sort of thing in mind. Instead of working through the operation queue like normal people, it simply switched repeatedly between previous state and current state - the idea being that you'd make a change that you weren't certain of, then press the key repeatedly to see before and after. No need to think. Thinking isn't appropriate here anyway. Just let your eyes look at what they're seeing.)

A new way of doing git diff, leave both versions of the code side by side and cross your eyes.

by a1o 2y ago

A new way of doing git diff, leave both versions of the code side by side and cross your eyes.

louiechristie 2y ago

My thoughts exactly. Could be done with a git diff in a VR headset

xattt 2y ago
If you’re already spending the computing effort to create the VR image… /s

justahuman74 2y ago

I sure didn't expect there to be a plausibly work-related angle when I came to this thread

bicx 2y ago

New business idea: git diff, but it uses Mechanical Turk to hire an army of cross-eyed diff spotters.

waffletower 2y ago
There is a wonderful stable diffusion prompt here.
deleted 2y ago
[deleted]

satvikpendem 2y ago

Somewhat related, but I've been using the Semantic Diff extension in VSCode, works better than standard git diff.

deleted 2y ago
[deleted]

deleted 2y ago

[deleted]

tom_ 2y ago

It sounds like you mock, but: you can do this, or near enough, and you can do it already, and it works really well! 0. Pick suitable tool. Firefox works. Notepad++ works. GIMP works. Emacs, not so much, but if you use Emacs, you know that you can fix this 1. Load file A into a tab 2. Load file B into a tab 3. Close all other tabs 4. Hold down the tab switch shortcut key and note the result For images this is actually pretty decent and I've used it a lot. Good for figuring out what the differences actually are when your image-based tests fail, and similarly after making a speculative change. Let your eyes do the difference operation for you. That's what they're there for. For text: you'd be better served by some other kind of tool. But text is just an image with letters in it, so the same principle applies. It does work! (I've previously read a blog post, link to which I of course now can't find, about how old-style Photoshop undo was designed with this sort of thing in mind. Instead of working through the operation queue like normal people, it simply switched repeatedly between previous state and current state - the idea being that you'd make a change that you weren't certain of, then press the key repeatedly to see before and after. No need to think. Thinking isn't appropriate here anyway. Just let your eyes look at what they're seeing.)