4 ms·

I would say interactive use is good. Not hard to configure prompts. Stability (in the sense of not crashing) is decent, it's been a long time since I've crashe

I would say interactive use is good. Not hard to configure prompts. Stability (in the sense of not crashing) is decent, it's been a long time since I've crashed Nushell. We do get the occasional crashing bug filed but most of those are in areas like our completion engine rather than interacting with external tools. OTOH, command design and language are not entirely stable; we are still pre-1.0 and we do make breaking changes fairly often. (I work on Nushell)

oblio 4y ago
> (I work on Nushell) Ooooh! Awesome! Thank you for your great work, I'd have 2 big questions: 1. Do you have any visibility into when things should stabilize enough for a 1.0 release? 1 year? 5 years? Impossible to say? 2. And the be-all-end-all of Linux distro packaging, Debian. Any plans to include it into Debian? Usually when this happens the package propagates to many, many downstream distributions, such as Ubuntu & family.
- ripley12 4y ago
  I'm not sure when we'll be ready for 1.0 (at which point we will commit to stability in the language etc.), but I would guess 1-2 years based on the work we want to do and the pace of contributions. Not sure about Debian. We generally rely on the community for distro packaging. Right now Homebrew is the easiest way to install Nu on most Linux distros.
mkingston 4y ago
Thank you! I've been using Nushell for a couple of weeks and at this point I don't see myself going back. Modern configuration. Great interactive usage (structured data, mostly!). I thought I'd like it, but more so than expected so far. The one shortcoming I've encountered so far is that some built-in functions seem to buffer all their input before producing any output, meaning I can't e.g. tail + filter logs. A fairly simple example: journalctl -xefu systemd-networkd-wait-online.service | lines | filter {|in| $in =~ 'start'} only produces output when I interrupt (ctrl+c). Is this expected?
- ripley12 4y ago
  Ahh, streaming. This is an area I've been working on; there are still lots of places where we collect data when we should stream it instead. In general, if you think "that should be able to stream" but it doesn't, that's probably a bug and worth filing an issue. I can reproduce your issue, I suspect that `filter` is collecting its input when it shouldn't. It's not totally clear why from looking at the code. If you can file an issue that would be appreciated, if not I'll try to do so later today. We have a tag for streaming issues: https://github.com/nushell/nushell/issues?q=is%3Aissue+is%3Aopen+label%3Astreaming https://github.com/nushell/nushell/issues?q=is%3Aissue+is%3A...
  - mkingston 4y ago
    Thanks for the reply. Upon further inspection, it looks like it's `lines`. It might also be `filter` but I haven't quickly come up with a way to determine whether that's the case. I opened an issue: https://github.com/nushell/nushell/issues/8016 https://github.com/nushell/nushell/issues/8016 I couldn't apply labels myself, I don't think.

oblio 4y ago

> (I work on Nushell) Ooooh! Awesome! Thank you for your great work, I'd have 2 big questions: 1. Do you have any visibility into when things should stabilize enough for a 1.0 release? 1 year? 5 years? Impossible to say? 2. And the be-all-end-all of Linux distro packaging, Debian. Any plans to include it into Debian? Usually when this happens the package propagates to many, many downstream distributions, such as Ubuntu & family.

ripley12 4y ago
I'm not sure when we'll be ready for 1.0 (at which point we will commit to stability in the language etc.), but I would guess 1-2 years based on the work we want to do and the pace of contributions. Not sure about Debian. We generally rely on the community for distro packaging. Right now Homebrew is the easiest way to install Nu on most Linux distros.

mkingston 4y ago

Thank you! I've been using Nushell for a couple of weeks and at this point I don't see myself going back. Modern configuration. Great interactive usage (structured data, mostly!). I thought I'd like it, but more so than expected so far. The one shortcoming I've encountered so far is that some built-in functions seem to buffer all their input before producing any output, meaning I can't e.g. tail + filter logs. A fairly simple example: journalctl -xefu systemd-networkd-wait-online.service | lines | filter {|in| $in =~ 'start'} only produces output when I interrupt (ctrl+c). Is this expected?

ripley12 4y ago
Ahh, streaming. This is an area I've been working on; there are still lots of places where we collect data when we should stream it instead. In general, if you think "that should be able to stream" but it doesn't, that's probably a bug and worth filing an issue. I can reproduce your issue, I suspect that `filter` is collecting its input when it shouldn't. It's not totally clear why from looking at the code. If you can file an issue that would be appreciated, if not I'll try to do so later today. We have a tag for streaming issues: https://github.com/nushell/nushell/issues?q=is%3Aissue+is%3Aopen+label%3Astreaming https://github.com/nushell/nushell/issues?q=is%3Aissue+is%3A...
- mkingston 4y ago
  Thanks for the reply. Upon further inspection, it looks like it's `lines`. It might also be `filter` but I haven't quickly come up with a way to determine whether that's the case. I opened an issue: https://github.com/nushell/nushell/issues/8016 https://github.com/nushell/nushell/issues/8016 I couldn't apply labels myself, I don't think.