3 ms·
For me: No. I feel like powershell tried exactly that and i don't like it. That may be in the end just depend on execution though. But powershell e.g. prints e
by lawl 6y ago
For me: No. I feel like powershell tried exactly that and i don't like it. That may be in the end just depend on execution though.
But powershell e.g. prints errors that look like stacktraces (it's been a few years i don't remember exactly) with type information. And while that may be desirable to some, when using bash i'm using a UI as a user and not programming and i don't want to read a stacktrace. I want an error message in english telling me what's wrong.
- little_panda 6y agoThere is a try/catch/finally mechanism in powershell: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_try_catch_finally?view=powershell-7.1 https://docs.microsoft.com/en-us/powershell/module/microsoft... However, it is quirky to set up and I don't remember the details now, it doesn't handle the errors out of the box for sure. I would still prefer powershell over bash (or god forbid, cmd) any day.
- quantified 6y agoSure. Is that how all REPLs behave? I have a feeling there is a lot of latitude for tuning the ergonomics.