Nushell core team meeting 2022-07-06

Attendees

Darren
Michael
Jakub
Reilly
Stefan

Topics

Trying to use discord for the team meetings

core-chat: Should work with the core-team role

Random video and audio dropouts

tabled backend for the table

zhiburt/tabled, zhiburt has been very active in the ANSI rust field and is very responsive

How to proceed with bugs we find -> maybe add a label for our issues

But should not contain show stoppers -> good for landing

Performance not benchmarked in all cases but nothing noticeable in small cases.

Jakub created a big case: 10x slower

Splitting up functionality into separate crates/modules/plugins

Benefits: Reduce binary size, improve build performance, WASM use case, embedded scripting use

Q: Can we delineate the core more clearly

Crates with build features should be a good compromise

But the default features people expect should not be pulled unexpectedly

Plugins are a build hassle and the interface is tricky

Having a core crate set would be great as a DSL/embedded scripting language for other Rust projects (Michael has performed some experiments cutting 200 crates from the dependency tree)

Separate repos are probably still cumbersome (e.g. release nu-ansi-term > reedline > nushel)

nana

Performance issues?

Can we get some more webdev experienced contributors

Hooks update from Jakub

Will support both strings and blocks. There will be an optional condition field to determine if the hook should run or not.

Tangent: Can we have modules for file formats

Fetching meta data from different binary files (metadata might be the first interesting aspect)
Inspired by JT's png parsing video: https://www.youtube.com/watch?v=6i4FRJ-3kkY