4 ms·
I empathize with a lot of this. With experience and knowledge it's easy to recognize why and how these things happen, to point them out, and to call the author
by starkparker 3y ago
I empathize with a lot of this. With experience and knowledge it's easy to recognize why and how these things happen, to point them out, and to call the author wrong. But I also remember being new to tools and not understanding how arbitrary they seem to be, in that they can understand what I want to do with uncanny precision but simultaneously refuse to do it. Things like exiting vim are the gold standard of this.[1]
But:
> Either support the feature, guide the user toward a better solution, or do nothing.
The first two examples _explicitly_ guide the user toward better solutions. That's much more than many tools do. If the Python repl behavior isn't "guide the user toward a better solution" in both letter and spirit, I'd love to know why.
There are much lower-hanging fruit than these examples, which makes a good point harder to agree with.
1: One of the first-page Google results for me on quitting vim is somehow this HN comment thread from 2017, in which the Python repl behavior catches strays with almost identical arguments as this article. https://news.ycombinator.com/item?id=14403297 https://news.ycombinator.com/item?id=14403297