The fact that it doesn't support your particular preferred syntax doesn't mean it's not production-ready.

> your particular preferred syntax

I think it's called POSIX.

You seem to be making some sort of argument, I just don't know what it is. Are you saying that fish is not production ready because it's not POSIX-compatible?

It's still not POSIX compatible, deliberately.

I‘m not switching to fish because of its lack of POSIX compliancy. This is a valid complaint.

It is!

But calling it "getting closer to production readiness" feels a tad insulting.

It's probably just a bit of snark, so it's not worth getting up in arms about, but it's not really friendly phrasing.

Fish uses (and still supports) `command1; and command2` instead of `command1 && command2` (and similarly for `||`/`or` and `!`/`not`).

The syntax is different, the semantics are the same.

It's 13 years old it's been production ready for a very long time. Using your preferred syntax != production ready.

If you feel productive with your current shell, stick with it, it is definitely a performance hit when switching shells. That being said, if you have a weekend, go for it, I won't switch back.