| Pronouns | they/them |
| Website | https://www.jntrnr.com |
| Github | https://github.com/jntrnr |
| YouTube | https://www.youtube.com/@SystemsWithJT |
Looking forward to them adding things like search/replace. It is evolving quickly, though. I'm excited to see where it'll go.
the book is pretty good (though I'm probably biased, as I helped with it)
Depending on your learning style, you might also like: https://github.com/rust-lang/rustlings
shout-outs to NES emu authors! 🙌
yeah, I tend to just go right to the docs for the crates, rather than use books that mention how to use crates.
For the upcoming version of The Rust Programming Language, they are making sure to remove as much as possible that refers to specific external crates because individual crates evolve faster than books do. Instead, I think they just point readers to the specific crates to learn more.
Definitely a bit of a bump in the road/trade-off between books and crates.
lol. some shells make some "interesting" syntax choices 😅
Parens would be a breaking change, but it's possible that's a change we want to make in order to get other kinds of syntax options.
And yeah, if we went with `out>` we'd have `err>` too. They may look a little odd at first but tbh, it took me years to be able to remember what `1` and `2` and things like `2>&1` even mean.
A juicy design puzzle for #nushell:
We're starting to add more support for "bashisms" - syntax that Bash folks would be familiar with.
Today, I tried adding the `>` for redirection. Unfortunately, that's also greater than (eg `3 > 2`). An example like `| where $a > $b` could then be parsed two separate ways.
Should we require parens on conditions? Or, should we not use `>` but instead us something else? (maybe `>>` or `out>` or yet another option?)
feeling similar. I like it, but this seems to have way more energy. Perhaps over time it'll grow?
Same! I need to dig through your new videos but I've been heads-down seeing if I can point Nushell in the direction of a 1.0.
