@boomzilla said in Software disenchantment:
Do you mean the concept of a post commit hook or the way that git implements them?
Kind of both.
The concept could be done well if Git had a well-defined plug-in system with well-defined input and output formats and then hooks were implemented as plug-ins following that standard.
But Git doesn't do that. What it does is garbage.
@boomzilla said in Software disenchantment:
I'm unclear on what you mean based on the stuff above where you asked how the GUI could convey information about this process. So I'm asking instead of attempting to mind read.
The point is post-commit hooks can output messages, right? But right now there's no way to display those messages in a reasonable fashion in a GUI, because there's absolutely no format defined for them.
So if you're writing a GUI, you have two choices:
- Just show a fucking dialog box with the output of the post-commit hook in a big-ass text field and just hope and pray the hook outputs something reasonable and actionable
- Don't support them at all
(Most choose option 2, but I think SourceTree, the shittiest of shitty Git GUI clients, does the former.)