News for hackers. Stuff that matters.
Re:Escaping from Anaconda (Python) by extr on Monday September 02, 2024 @03:18PM (#41428063)
Spoken like someone who has never had to teach non-programmers from complete scratch. Yes it would be ideal to spend hours setting up the conceptual framework for environment management. But now you’re teaching a “Python conceptual frameworks” course instead of whatever you were originally supposed to talk about (usually some specific package or workflow). It’s liable to be frustrating and feel irrelevant for people who are not and will not be career programmers. Better to get going quick and circle back around to that stuff if/when necessary and it’s properly motivated.

This is why R actually really great btw, R/RStudio make it insanely easy to “just get going” with a package installer UI.

Re:Escaping from Anaconda (Python) by greazy on Monday September 02, 2024 @03:47PM (#41428255)
Agreed this is why R up take is so high compared to python in non CS fields. But I've seen people quickly hit a bottleneck of deps hell and flounder because the tools RStudio provides are (imo) not great. Posit (Rstudio) was too heavily invested in their IDE. I'm glad to see them branching out into (see their up coming ide positron).
Re:Escaping from Anaconda (Python) by YWall39 on Monday September 02, 2024 @04:39PM (#41428615)
yes, number 1 reason why the researchers around me pick R. RStudio just works.

I had to run someone's 10 year old R workflow last week. Ran perfectly.

Last years python code will not run unless someone was careful enough to make a requirements.txt. Try explaining that to the non computer scientists. My python support colleague runs into that constantly. She is not a happy support person.

Re:Escaping from Anaconda (Python) by hot_gril on Tuesday September 03, 2024 @02:04AM (#41431755)
Same with NodeJS. The way it does package management is more "Pythonic" than Python. Even importing your own files is simpler, just relative paths instead of the __init__.py and packages.