but taking the time to get comfortable with a bad UI has often really paid off for me
I'll often keep using an older tool with a worse UI because it's more stable, or more actively maintained, or has more features, or has more examples available, or my friends use it
it's still important to acknowledge that the UI is in fact bad even if I'm pretty comfortable with it now
mine would be something like, "git, you know what happens when you act like this. This is for your own good. This is gonna hurt me more than it hurts you"
One of the reasons why I have eschewed modern IDE’s and essentially all graphical wrappers around command line tools is because I will inevitably need to do something that isn’t supported by the wrapper and I have to fall back to the CLI and if I have to do it at all I’d rather just not have to change between interfaces at all.
@b0rk I once heard something that I think about nearly once a week now:
Videogames are just bad user interfaces.
They didn't mean the games have bad GUIs. They meant that the reason games are fun is because we enjoy overcoming the challenges posed by intermediate obstacles between us and our ultimate goals. I think this explains a lot about why awkward command line UIs persist. We enjoy the process of learning them and once learned they aren't hard anymore.
@b0rk I think that's the healthy way to approach this, and we've normalised a lot of pretty unhealthy views and practices with regards to lauding and even prosealotysing tools with bad UI just through our own sunk cost of having put in the tedious and frustrating work to learn them.
Add comment