5 minutes for every change definitely justifies language/library selection based on optimising for compute time. I do operations that are nowdays computationall

5 minutes for every change definitely justifies language/library selection based on optimising for compute time. I do operations that are nowdays computationally trivial, for example, tinkering with model specifications, which, even for rows in the millions, typically takes <1 second of compute time. A typical workflow would involve minutes/hours of wrangling, minutes/hours of model spec, and perhaps only a small number of minutes actually waiting for computation to complete. With some exceptions, of course. Btw thanks for a very interesting take on a generally neglected topic (language choice for economists). I hope you do more and deeper discussion on this as I think a lot of economists never make it to open source and get stuck using whatever they learned in university (eviews or spss).