In a way, true, but if you want to work in the corporate world, should be "learn ksh". Very little difference between them, and will force you to write portable scripts. Using bashisms will make things a bit harder for you.
Most proprietary software companies like to buy uses ksh. I support a few of them now where I work, all uses ksh.
> Most proprietary software companies like to buy uses ksh. I support a few of them now where I work, all uses ksh.
I've never known companies to buy large software products written in a shell language, but on top of that haver rarely if ever come across ksh in a professional setting.
I can imagine this being the case in some industry niche, but don't think "most" is appropriate.
In a way, true, but if you want to work in the corporate world, should be "learn ksh". Very little difference between them, and will force you to write portable scripts. Using bashisms will make things a bit harder for you.
Most proprietary software companies like to buy uses ksh. I support a few of them now where I work, all uses ksh.