Nushell core team meeting 2023-06-14

Attendees

• Antoine
• Darren
• Michael
• Stefan
• JT

Agenda

• Release cycle
• nu-cmd crate topology proposal, related to nushell/nushell#9404
  • #9429 for parallel compilation with the existing crates
• archive stale channels in the Discord: #project-nana and #triage ?
• (we'll figure this out) cargo in the CI and --workspace: related to nushell/nushell#9425
  do we want to add extra to the CI in order to run the nu-cmd-extra tests ?
  • Stefan: yes there is no way around that!
  • @amtoine: but we already have the --workspace options triggered
• bloat in binary size and compile time
• uutil and friends

Discussed Topics

Detour: serde and bloat

• maybe ShellError is the culprit for the large compile size for serde derives
  • some no inline trick did not cut it as an easy fix

release cycle

change the cycle only after next release to update users in the next blog post.
we do not want to surprise anyone.

the main benefit is to buy us more time to polish and have a solid 1.0.

going from 3 to 4 delays the 0.100 release by around 4 months.

Decision message on discord/blog, make the regular release and then try the 4 week cadence

thinking about milestone framework for 1.0

• commands
• engine rework
  • parser
  • bloat
• config
• standard library
• plugins?

uutils and nushell

uutils/coreutils

s side to have the option to use uutils internals without having to use the POSIX frontend and replace it with a nu front

https://twitter.com/_vkaku/status/1668752465737715712 Twitter thread kicking of potential collab

Also a potential option to have more posix compatibility where needed.

Darren: challenge to shim the output (as they can freely print to STDOUT) while we have to channel the data into the correct format.

Can using JSON be a compromise

nu-cmd-base

We decided to have a new crate called nu-cmd-base which would be the place for all of the core datastructures that need a home. The other alternative was to add more stuff to nu-utils which is not ideal.

This crate nu-cmd-base will be used for helper methods, traits, structs that are used by all of our commands.

There will be NO commands in nu-cmd-base.

Issues

Image Not Showing Possible Reasons

• The image file may be corrupted
• The server hosting the image is unavailable
• The image path is incorrect
• The image format is not supported

Learn More →

the issues which needs-core-team-attention

Image Not Showing Possible Reasons

• The image file may be corrupted
• The server hosting the image is unavailable
• The image path is incorrect
• The image format is not supported

Learn More →

Note
to list all the PRs currently opened in nushell/nushell:

gh pr list --json url,number,author,title
| from json
| each {|i|
    $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
}
| reverse
| to text