Because I need the scripts and snippets I write for my repos to work for other developers, I'm going to write them to be bash compatible. That applies also to scripts and snippets written by others that I consume.
So if a shell is not bash syntax compatible, then it really has to offer some astonishingly useful features to offset my having to translate and map the scripts I need to run for it.
Murex does not interpret "$(cmd args)". So unfortunately, I cannot use it. I know it's not fair, and I know that is promoting a lock-in of what shells can do, but I need to get shit done I'm afraid.
moondev 1 hours ago [-]
You should consider putting a shebang at the top of your scripts instead of leaving it to fate
liampulles 1 hours ago [-]
I do this for all the scripts I write. That does cover one of the scenarios I covered above, which is valid.
rafram 1 hours ago [-]
Then there’s no reason you can’t use a different shell as your interactive shell, while running your scripts in bash.
liampulles 1 hours ago [-]
For me to develop my scripts it would help alot if my interactive shell supports the syntax as well. I mean you are right of course, I CAN do that, but it then becomes a tradeoff question again of whether this non-compatible interactive shell has sufficient niceties.
MangoToupe 1 hours ago [-]
I just write everything in fish and have an LLM translate it to bash. Freed up a couple brain cells for more useful things for sure.
kitd 4 hours ago [-]
Interesting. Looks similar to nushell [1] which also is data-encoding-aware.
Thanks for pointing it out. I've tried both as interactive shells for a few minutes. Murex seems to have a more minimalist approach that works well as a drop-in replacement.
However, I have trouble understanding some design decision, such as inventing redundant keywords. And I've spotted bugs in boths (e.g. ls --literal fails in nu, and the completion proposes it twice in Murex).
wyan 5 hours ago [-]
Wasn't Murex some sort of backend software for financial institutions?
Still is. It's a French/Lebanese corp based in Paris/Beirut. I worked there for a few years early in my career.
pasc1878 42 minutes ago [-]
Not just backend - it replaced the front end system I wrote for FX options (after I left the bank)
mikl 5 hours ago [-]
Maybe I’m just not the target audience, but looking at the front page, I don’t see what actual problems this solves. The claims sound nice, but without examples of what they mean in real world use, it’s not really compelling.
_notreallyme_ 5 hours ago [-]
I may be wrong, but it gives me some powershell vibe. Since it seems to be targeted for macOS, I would assume it "solves" the lack of powershell equivalent on Mac ?
Powershell 7+ (a long while ago named core) is the version you should use on ALL platforms, including Windows. It's just the most recent version.
"Core" gives off a vibe that it is some limited thingy. It's not, it's full PS.
rusk 4 hours ago [-]
Oh goody
oneeyedpigeon 3 hours ago [-]
What happened to the convention that shell names end in sh? There are:
grep sh$ /usr/share/dict/words | wc -l
1959
options available; surely we haven't exhausted them all?!
bckr 2 hours ago [-]
This is instead named for an animal with a shell
h33t-l4x0r 5 hours ago [-]
This looks interesting, I will consider switching if it's not sluggish like zsh was that one day I tried it.
iberator 5 hours ago [-]
Back in the 486 era? same here hehe
ksh for life :p
So if a shell is not bash syntax compatible, then it really has to offer some astonishingly useful features to offset my having to translate and map the scripts I need to run for it.
Murex does not interpret "$(cmd args)". So unfortunately, I cannot use it. I know it's not fair, and I know that is promoting a lock-in of what shells can do, but I need to get shit done I'm afraid.
[1] https://www.nushell.sh/
However, I have trouble understanding some design decision, such as inventing redundant keywords. And I've spotted bugs in boths (e.g. ls --literal fails in nu, and the completion proposes it twice in Murex).
NB story spoilers. <https://wiki.warframe.com/w/Murex>
https://learn.microsoft.com/en-us/powershell/scripting/insta...