Hacker News new | ask | show | jobs
by genocidicbunny 2 days ago
> artist should use any of the nice frontends that work on top of git and hide its verbosity.

Right up until something goes fucky. You know how many times I got messaged by someone dealing with vcs going wrong for them at a late hour in the evening? If I had a nickel for every time, I wouldn't be rich, but it probably would have bought me a gallon of gas.

It's not the verbosity strictly speaking. It is the minimal level of abstraction between you and the vcs and it can hardly be helped by a 'nice frontend' when things go wrong. And they will; they always do.

2 comments

> It is the minimal level of abstraction between you and the vcs and it can hardly be helped by a 'nice frontend' when things go wrong. And they will; they always do.

How is this different from any other piece of software ever? When things go wrong, the artist is stuck either way. The only solution is software that always works...

I don't understand - you arguing that artists should learn to use cli? if so, "programmish" git output is not a problem, because they already not just artist, they learned git.

But, for me this looks like this - if artist need to go to cli to solve some error, then this is bug or leaky abstraction in GUI client.