Working in Jupiter lab on a project, running the code block by block, then print-debugging, changing stuff and rerunning blocks. Is it just me, or notebooks are insanely bad IDEs. How the hell ppl write decent code in this environment? Whatever I do, it ends up an entangled mess. The only way to be sure is to restart the kernel every time I change something
=> More informations about this toot | More toots from kupac@functional.cafe
@kupac I am consistently surprised that the IDE is so useless and clunky, and that people seem to love it nevertheless. It is also incomprehensible to me that the file format is locked into one IDE, unlike just about any other language.
=> More informations about this toot | More toots from shabbychef@mastodon.xyz
@kupac I have all these same concerns about notebooks and more. I find #rmarkdown and #quarto much better than Jupyter, but they still suffer from similar problems.
Unless I am explicitly planning on compiling an HTML report, I tend to stay away from these literate programming tools.
=> More informations about this toot | More toots from jrhawley@scholar.social
@jrhawley
Exactly. The one I'm tempted to try and learn is org mode. It supports multiple languages, and can be used in a non-linear way -- as it should.
=> More informations about this toot | More toots from kupac@functional.cafe
@kupac I love orgmode for my personal writing, note-taking, and task management, but I have found it difficult to use for literate programming if you have any type of environment management.
If everything is installed globally, fantastic. Emacs can run whatever you need.
But if you use conda, Python venv, nix, or any other environment manager, you play this awkward game of environment-variable-foo and Emacs package management.
I haven't had good results here, but good luck to you if you try!
=> More informations about this toot | More toots from jrhawley@scholar.social
@kupac They have their usage. They are especially useful for data exploration and troubleshooting. They document what steps you have taken, and with some editing, they are good at authoring documentation or articles.
I found them useful while working with data
=> More informations about this toot | More toots from hugoestr@functional.cafe
@kupac using vscode to run jupyter notebooks is a less worse alternative, at least there are proper IDE features.
Though, judging by your username you might be a vim user and thus wouldn't touch vscode with a ten foot pole
(PS. edit : notebooks arn't for writing proper code, they are to put together some quick graphs/ideas)
=> More informations about this toot | More toots from Lurk@genomic.social
@kupac @shabbychef notebooks seem to have a very specific use case rather than being a general tool
=> More informations about this toot | More toots from ctrl@c.im This content has been proxied by September (ba2dc).Proxy Information
text/gemini