Have they found the right way to be inclusive of and handling old-style tools that only in/output text? That's usually a deciding factor in how improvements and new systems gain traction - that they are possible to introduce gradually and they deal with all existing programs.

I think it's pretty good.

It's easy to pipe text-speaking tools into Nu pipelines, and there's a built-in `lines` command that will split line-break-delimited text into a list of strings. From there you can use lots of tools to operate on each line.

Going from Nu data structures to raw lines of text is a little clumsier (`str collect (char newline)` IIRC) but I think that will get improved soon enough.

There's also a handy `detect columns` command that does a pretty good job of automatically converting text tables from old *nix/Windows tools into Nu tables.

Screams for -join operater.

You need to write a plugin in rust. The builtin scripting language isn't that good.

No. Plugins are just executables that communicate with Nu over stdin/stdout using JSON or Cap’n Proto; they can be written in any language.

In the article, they show how you can use any language to write a plugin.

Writing a plugin is an example of Nu not solving the problem in general - maybe you misunderstood my question