131–140 of 215 posts
Read this as "Nutshell", which would have been a really cool name for a shell.
Earlier quoted context omitted.
Many of these next-gen shells like Nushell are clearly (and sometimes explicitly) inspired equally by Fish and by PowerShell, and it shows. It's a brilliant combination!
I think the problem with this approach is that it breaks down at some point, and then your only option is to rewrite the entire thing in a real scripting language. I.e., there is no graceful scaling path.
And there's no hard constraint that would require this to "break down at some point". A well designed shell could also be a "real scripting language", all-in-one.
But the horrible CP/M and POSIX legacy of shell design doesn't help with that.
Earlier quoted context omitted.
Quite frequently? "Oh this operation turned out to take a while, I'll use pv instead of cat", or "oh what I grepped for wasn't in the current log, it's probably in the previous log that's gzipped, I'll replace 'cat current.log' with 'zcat previous.log'".
Sounds like you describe a interactive shell session, not stuff that happens in that script that was written for a specific purpose.
I like the idea of piping structured data between processes instead of streams of bytes, but that's what PowerShell is for. I don't think I've ever met another dev who likes PowerShell
I have. But they have never used bash, zsh, Fish, or NuShell.
I like the idea of piping structured data between processes instead of streams of bytes, but that's what PowerShell is for. I don't think I've ever met another dev who likes PowerShell
I'd actually like the ability to do either raw bytes (traditional) or structured bytes (the NuShell/PowerShell idea) in an "opt-in" scenario. This would also allow a smoother transition/lack of needing to fully commit right off the bat. I've considered writing wrappers for standard utilities in Bash/Zsh that accept and output structured data in JSON (or maybe a denser serialization format that can easily convert to J…
It basically sits somewhere between Powershell and Bash: typed pipelines like Powershell but without sacrificing familiarity with all the CLI commands you already use day in and day out.
https://github.com/lmorg/murex
As an aside, I’m about to drop a massive update in the next few days that will make the shell even more intuitive to use.
Earlier quoted context omitted.
What if someone starts from a clean slate. Which shell is better? That is the question. Old habits hold us back from progress in usability. Eventually if one system is better it should completely replace the old system. But only if it's better. What one power user deems as "useful" according to his own usage patterns shouldn't be a metric for measurement. I haven't played with nushell yet, but it actually seems more…
> What if someone starts from a clean slate. Which shell is better? Then they learn the better and end up having to learn bash anyway coz that's what runs on remote machines. There is also not that much to be gained. Common easy tasks might be easier to learn but just few percent faster in the end. Harder ones are faster by one-off script in "real" programming language most of the time. Harder repeatable one should n…
Is that actually still an issue these days with Docker containers and what not? How often do you access a remote server via SSH where you share an account with your colleagues and cannot install another shell next to bash? (So that bash could still be the default but you could switch on the fly.)
Earlier quoted context omitted.
Quite frequently? "Oh this operation turned out to take a while, I'll use pv instead of cat", or "oh what I grepped for wasn't in the current log, it's probably in the previous log that's gzipped, I'll replace 'cat current.log' with 'zcat previous.log'".
Sounds like you describe a interactive shell session, not stuff that happens in that script that was written for a specific purpose.
Earlier quoted context omitted.
>But most of all the cat way just aligns with my mental model more. Data flows left to right, if you catch my drift. Using ` out_file` (Though annoyingly this doesn't work for feeding input to while loops. `< <(echo a; echo b; echo c;) while read -r foo; do echo "$foo"; done` is invalid syntax; it needs to be `while read -r foo; do echo "$foo"; done < <(echo a; echo b; echo c;)`)
> Using ` If you showed that without context it would look like some prefix/lispy notation so no, you are just showing how bad it is
What's the story with not having a deb / flatpak / appimage or snap distribution? Just lack of resources to help package?
Don't think we've had any requests for those, but we'd welcome contributions if someone wants to make it happen. For now, Homebrew works if you want a cross-distro way to install Nu on x64 Linux.