'command -v' is POSIX!! I have always avoided it in favor of which because its output doesn't feel machine friendly.
Debian's Which Hunt
11–20 of 257 posts
Re: Debian's Which Hunt
#12'command -v' is POSIX!! I have always avoided it in favor of which because its output doesn't feel machine friendly.
What makes `command -v` not machine friendly? It seems to always output just the PATH, unlike type which tries to be human friendly.
Re: Debian's Which Hunt
#13Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
Re: Debian's Which Hunt
#14Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
> Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. In my opinion, this is a good thing. Aiming for increasing "market share for average consumers" usually implies focusing on the standard baseline of functionality. There is nothing wrong with this, but this invariably cuts off tinkerers and enthusiasts who care about playing with SDRs and LIDARs and other frin…
Seeing as mobile internet outstrips desktop internet, and Android is the majority of mobile internet devices, the Linux kernel runs under one of the top two pluralities of client side web browsing.
Re: Debian's Which Hunt
#15Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
> A proper transition plan would mean that I would never even notice this. One which would replace another and nothing would break. That is the sort of thing I expect to happen in Debian - we are generally good at this stuff, and it's a big reason for using the distro.
No tempest, no bikeshedding. That seems like the polar opposite of whatever you are criticizing.
Re: Debian's Which Hunt
#16Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
If you don't understand why something like this is important to get right, I'd suggest maybe finding out why other people do actually care about things like this.
Or maybe reflect on why Microsoft spends so much money and energy on backwards compatibility.
Re: Debian's Which Hunt
#17Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
It's ironic how a comment about 'bikeshedding' spawns five comments in the span of twenty minutes.
Re: Debian's Which Hunt
#18'command -v' is POSIX!! I have always avoided it in favor of which because its output doesn't feel machine friendly.
Re: Debian's Which Hunt
#19Wow, talk about a tempest in a tea kettle. Bikeshedding like this is why Linux will never achieve any significant market share for average consumers. (Because all that mental effort could have been spent on solving some real problem instead of philosophical conformity.)
Big opaque corporations definitely never spend way too much time in meetings over pointless things.
Re: Debian's Which Hunt
#20Seems like this is a case of Debian governance working as designed. I'm surprised that 'which' isn't POSIX though.