While I think it's cool to know the reasons behind the design decisions of something you love (such as Fish Shell), I highly doubt this individual's opinion on Fish Shell will be swayed by the information you find at https://fishshell.com/docs/current/design.html. Your use of the word "rant" makes me believe that. One of the things I've found most separates good programmers from shabby ones is maturity. Being mature enough to accept that there's often a time and place for everything. For example, I love functional programming and I dislike Java, but it'd be childish of me to claim object-oriented Java is awful and had no place in modern programming. So by all means, read up on the design decisions behind the `and` command versus a `&&` operator, but don't get your hopes up that this person will come around on their opinion.
On 10/18, John Chludzinski wrote:
I have someone who occasionally uses my machine and immediately begins complaining about fish. Latest rant is fish's use of 'and' and 'or' in lieu of && and ||. Is there a rationale for these design decisions?
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
