2 ms·
I think the crux of it is how much time you spend in the command line on your local machine. If it is substantial then picking a shell you're productive in is l
by hnlmorg 6y ago
I think the crux of it is how much time you spend in the command line on your local machine. If it is substantial then picking a shell you're productive in is little different to picking a graphical desktop environment (knowing that your colleagues could be running a different DE, or even OS). If the majority of your time in the command line is on other peoples machines and/or servers, then you're unlikely to see much, if any, gains picking an alternative shell on your local machine.
With regards to murex specifically, there's nothing stopping it from running on servers but pragmatically that's an unrealistic domain to target. What I'm focusing more on is a better experience for running DevOps / developer tools on an engineers local machine. The cost of that is portability - which is, understandably, a deal breaker for lots of people.