Pandas feels clunky coming from R. What about Haskell?
mchav.github.io
Pandas feels clunky coming from R. What about Haskell?
1–9 of 9 posts
Re: Pandas feels clunky coming from R. What about Haskell?
#2Re: Pandas feels clunky coming from R. What about Haskell?
#3Re: Pandas feels clunky coming from R. What about Haskell?
#4Although not quite the same without a pipe operator, https://pola.rs was an improvement for me when missing the R dataframe syntax.
Re: Pandas feels clunky coming from R. What about Haskell?
#5that ended rather abruptly?
Re: Pandas feels clunky coming from R. What about Haskell?
#6groupby has an as_index parameter for this very purpose
> Deducting the discount
You focus on doing the subtraction during the group by. Is there any good reason for this? You could either do it as a step before, or after summing up both columns. Putting too many things into one command is not good practice yet you benchmark the language based on how easy it is to do said bad practice
Re: Pandas feels clunky coming from R. What about Haskell?
#7> This has a great SQL-ish API. Python is similar but starts to be a little clunky since it requires you to think about indices: groupby has an as_index parameter for this very purpose > Deducting the discount You focus on doing the subtraction during the group by. Is there any good reason for this? You could either do it as a step before, or after summing up both columns. Putting too many things into one command is…
Re: Pandas feels clunky coming from R. What about Haskell?
#8> This has a great SQL-ish API. Python is similar but starts to be a little clunky since it requires you to think about indices: groupby has an as_index parameter for this very purpose > Deducting the discount You focus on doing the subtraction during the group by. Is there any good reason for this? You could either do it as a step before, or after summing up both columns. Putting too many things into one command is…
I think the original author picked this example to broadly illustrate how easy it is to make ad hoc changes to your query without worrying about lot about implementation details. Polars, for example, converges on a similar API and gives you the flexibility. You can iterate then refactor easily later to what you consider good practice.