4 ms·

reading only this post, is nushell just an implicit awk after each pipe, that already know the output format of a few common programs? or something more than th

reading only this post, is nushell just an implicit awk after each pipe, that already know the output format of a few common programs? or something more than that?

algorithmsRcool 6y ago
Think powershell, but built in rust, posix first and better at processing data(xml, csv, json, ...)
- xfer 6y ago
  I looked at the book, currently it is nowhere close to powershell. As far as i can tell no way to define any function/commands(you have to write plugins in another language, make an executable??). It supports pipeline, has a large amounts of built-in operators/commands(probably enough to be usable as a shell) and built-in parsers for a few formats(how does one write support for another data format?). Maybe in future it will address these questions.
  - ChrisSD 6y ago
    The linked post is explicitly about that: > Looking at Nu today, you can see some common parts of languages like `if` or `open`, but it doesn’t yet feel like there’s enough syntax to build up full programs. You can’t define your own commands, your own variables, and you can’t build out a project across multiple files. We’re working to address all of these limitations so that Nu can function not only for one-liners, but also for much more.
- emersonrsantos 6y ago
  But Nushell is POSIX compliant?
eigenrick 6y ago
It is quite a bit more in-depth than that.. It really is more of a structured data pipeline in a programming environment. It's more like Spark than Awk. There are bulti-in methods like `parse` and `split`, `format` which can provide awk-like behavior. However, there are many other built-in methods which operate on tables, floats, vectors and integers. I actually have a ticket in to make some of the parsing behavior a bit more "awk like" (https://github.com/nushell/nushell/issues/2375 https://github.com/nushell/nushell/issues/2375)

reading only this post, is nushell just an implicit awk after each pipe, that already know the output format of a few common programs? or something more than that?

algorithmsRcool 6y ago

Think powershell, but built in rust, posix first and better at processing data(xml, csv, json, ...)

xfer 6y ago
I looked at the book, currently it is nowhere close to powershell. As far as i can tell no way to define any function/commands(you have to write plugins in another language, make an executable??). It supports pipeline, has a large amounts of built-in operators/commands(probably enough to be usable as a shell) and built-in parsers for a few formats(how does one write support for another data format?). Maybe in future it will address these questions.
- ChrisSD 6y ago
  The linked post is explicitly about that: > Looking at Nu today, you can see some common parts of languages like `if` or `open`, but it doesn’t yet feel like there’s enough syntax to build up full programs. You can’t define your own commands, your own variables, and you can’t build out a project across multiple files. We’re working to address all of these limitations so that Nu can function not only for one-liners, but also for much more.
emersonrsantos 6y ago
But Nushell is POSIX compliant?

eigenrick 6y ago

It is quite a bit more in-depth than that.. It really is more of a structured data pipeline in a programming environment. It's more like Spark than Awk. There are bulti-in methods like `parse` and `split`, `format` which can provide awk-like behavior. However, there are many other built-in methods which operate on tables, floats, vectors and integers. I actually have a ticket in to make some of the parsing behavior a bit more "awk like" (https://github.com/nushell/nushell/issues/2375 https://github.com/nushell/nushell/issues/2375)