One thing that came to me as news is that the command which—which is the de-facto tool to
find the path of an executable—is not POSIX compliant. The recent Debian debacle1 around
which brought it to my attention. The POSIX-compliant way of finding an executable program
is command -v, which is usually built into most of the shells.
So, instead of doing this:
which python3.12
Do this:
command -v which python3.12
~~~
Recent posts
- Preventing accidental struct copies in Go
- Go 1.24's "tool" directive
- Capturing console output in Go tests
- Deferred teardown closure in Go testing
- Three flavors of sorting Go slices
- Nil comparisons and Go interface
- Stacked middleware vs embedded delegation in Go
- Why does Go's io.Reader have such a weird signature?
- Go slice gotchas
- The domain knowledge dilemma