Marc Garcia

`select` will offer a much better syntax with method chaining, that's the motivation for having both `select` and `filter`. I can show you with an example if needed.

> Maybe I'm missing something, but using `df[["col1", "col2"]]` in a method chain is equivalent to using `df.select("col1", "col2")` in a method chain. You're right, it's the inconsistency with everything...

Thanks for the feedback. This is something that Polars allows and I wanted to show as it makes the example cleaner. But surely not part of this PR, or any...

You are correct @Dr-Irv, and of course `df[["col1", "col2"]]` will stay. I wouldn't say it's for people coming from PySpark or Polars, even if it surely will make life easier...

It's just for method chaining that I think it's better. I don't think in isolation select is better. It's more explicit, but I don't think we should rewrite examples or...

We discussed this in today's call, and while not the perfect solution, everybody agreed that allowing both `*args` and a list is better than the alternatives. I fully agree that...

Thanks @jbrockmendel for the comment. We discussed your point of view which you previously shared, on wanting just one way. I think everybody in the call was also -1 in...

Updated the PR to implement what we agreed. The code and behavior seem very reasonable to me. Feedback welcome.

If I understand correctly that it'd be better to not support example 2 (if example 1 is considered the best API, which I think in isolation mostly everybody thinks), then...

If anyone else has interest in the `select` / `filter` stuff, please go ahead, happy to hand over it. I already spent more time that I wanted in this, and...