Right, the system() function in C, which PHP probably uses, and is os.system() in Python, is DEFINED to run /bin/sh. You never know when a program might call it (although I agree it is almost always bad practice to use it -- use fork/exec instead.)
So basically you should never make /bin/sh fish, because then you will no longer have a Unix system (according to POSIX).
Not sure I understand what you mean. /bin/sh is the system shell, I don't believe it's possible to make it fish unless you change the symlink itself.
On ubuntu, /bin/sh is always dash and it's not possible to change without changing the symlink:
https://wiki.ubuntu.com/DashAsBinSh
So, if you use chsh to make your shell fish, it would have no effect on os.system or the system function in C.
PHP somewhat takes the user’s login shell, so I guess it’s yet a different system.
If it was taking /bin/sh it would have been fine actually.
Don't blame the rest of the world for PHP's brain damage.
That's just lazy programming, and if anything, we should have more incompatible shells so that developers will start to write their programs to stop shelling out and run individual programs, or if they do shell out, actually declare the shell you're using at that point and don't assume it will be sh compatible.
Having bash compatibility is a quality of life feature, no need to debug all the werid cases where it breaks for purely syntax reasons.