All source comparison tools suck. Sighs.
Conversation
Notices
-
Embed this notice
Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Tuesday, 22-Apr-2025 22:57:57 JST Alfred M. Szmidt
-
Embed this notice
Christian Lynbech (mapcar@mastodon.sdf.org)'s status on Tuesday, 22-Apr-2025 23:55:49 JST Christian Lynbech
@amszmidt Nonsense, you are just using the wrong tools.
Print out the two versions onto punch cards, overlay two cards and hold them up in front of a strong lamp. Problem solved.
😊
Alfred M. Szmidt repeated this. -
Embed this notice
Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Wednesday, 23-Apr-2025 04:15:07 JST Alfred M. Szmidt
@mapcar Worst part, is that .. given enough granularity ... where a function per card, this would work _REALLY_ well, since it would just be a matter of light refraction.
My biggest pet peeve is when you have movement in files, function FOO got moved from before BAR to after BAR. Or into another file, or some such.
What I'd like to see is "logical" movement, something #GNU ChangeLog always did very good at ...
-
Embed this notice
Alfred M. Szmidt (amszmidt@mastodon.social)'s status on Wednesday, 23-Apr-2025 04:20:32 JST Alfred M. Szmidt
@mapcar For example, @wilfredh difftastic is awesome .. for very small change sets. If you have two very diverged code bases (might not be the most common thing, so .. hey), and you want to see more high level movement of code, no program I know does the work needed.
This could be useful for other purposes too .. but I guess this is kinda niche ...
-
Embed this notice
Weekend Editor (weekend_editor@mathstodon.xyz)'s status on Wednesday, 23-Apr-2025 05:17:17 JST Weekend Editor
Ok, I'm actually old enough to have done that! It worked really well, but I was so frustrated in the moment I didn't take time to be glad about it.
But basically, you've re-invented the old-time astronomy instrument called the blink comparator.
-
Embed this notice