# Nushell core team meeting 2023-09-13
## Attendees
- Darren
- Reilly
- JT
- Michael
- Antoine
- Stefan
- Windsoilder
- Jakub

## Agenda
- [x] Config location ([#8682](https://github.com/nushell/nushell/pull/8682))
- Confirm: are we OK with a "Use the platform specific directory if it exists, otherwise use `~/.config/nushell` on every platform" approach?
- [x] type naming inconsistencies ([#10332](https://github.com/nushell/nushell/issues/10332))
- progress on `decimal` -> `float`
- rename *date* to *datetime* ([#10298](https://github.com/nushell/nushell/pull/10298))
- what about `null` and `$nothing`?
- [x] Removing operator overloads
- int * list ([#10292](https://github.com/nushell/nushell/pull/10292))
- int * string ([#10293](https://github.com/nushell/nushell/pull/10293))
- How should a `repeat` command behave?
- `[a b c] | repeat 2`
- `[a b c a b c]`
- `[[a b c] [a b c]]`
- [x] *extra* and *dataframe* as plugins ([#10322](https://github.com/nushell/nushell/issues/10322))
- [x] plan with `echo` (comment in [#10221](https://github.com/nushell/nushell/issues/10221#issuecomment-1710493584))
- [x] When to post Darren's blog post
- [ ] plan for how to use results from latest survey to drive future action items of what folks can do to make nushell better. This way we leverage the results of the survey...

## Discussed Topics

### Quick topic: plugin example in the contrib book
- porting to different languages
- edhowland has been playing with a ruby example of the current example
- Storm wants to get the contributor book back up

- Darren found approx 50 plugins on cargo.
- any refactor will trigger major work
- only a fraction up to date

### `extra` or `dataframe` commands as plugins

- dataframe with its big data blobs hard to send over the json wire
- would require the plugin to keep the data around internally.
- would have to be long running
- Storm: different strategies for providing distributions:
- plugins
- users that have nushell already downloaded (from there distro package manager)
- missing commands, we tell `--features extra`
- We have a lot of users, that don't have (recent) Rust on the system
- crates with very standardized interface
- requirese building
- could this be just config files?
- the interface is
- JT: this are expert users that recompile nushell

### Config location

[Reilly's comment on the PR thread](https://github.com/nushell/nushell/pull/8682#issuecomment-1710806530)
Reilly: initially wanted to just start with point 1
But PR has a different order compared to Reilly's proposal

Darren: point three is the point of compromise for me

Reilly goes ahead: Check OS first, then ~/.config, and use ~/.config if neither are present

### Type inconsistencies

#### -> `float`
Going ahead to all `float`

#### `datetime` vs `date`

JT: type name should be `datetime` (and everything that follows from it)

The truth is `datetime`
dataframe have both :P

#### `$nothing`
just needs a good deprecation strategy and implementation

### Operator overloads removal
Pythonisms have been removed

How should `repeat` look like:
- prelude
- repeats inner or continues an iterator.
- repeating of scalars
- what is the behavior `1..5 | repeat 3`

Agreement on prelude

### `echo` - piping vs printing

Bug to fix around redirection in `let` (for externals: <https://github.com/nushell/nushell/issues/9767>)

Behavior around function: `def foo [] { echo "bar"; ignore }`

Kubouch: behavior is really subtle. Maybe worth keeping around `print` to be explicit so you don't have to worry about the corner cases

legacy on `echo` is freaking strong, speedbump for many new users (?9th most used command)

### Blog post `uutils` collab from Darren

post ahead of time and announce the release date