jupyterlab-gitplus VS mise

If you are in need of a diff tool for jupter notebooks use https://www.reviewnb.com/ and for word documents use https://www.simuldocs.com/

- GitHub PR code reviews with ReviewNB[4]

Alternatively, if you don't care about cell outputs then Jupytext[5]

Disclaimer: I built ReviewNB. It's a completely bootstrapped business, 5 years in the making and now used by leading DS teams at Meta, AWS, NASA JPL, AirBnB, Lyft, Affirm, AMD, Microsoft & more (https://www.reviewnb.com/#customers)

[1] https://github.com/jupyterlab/jupyterlab-git

Already a GitHub plugin that does this very nicely: ReviewNB

For version control: https://www.reviewnb.com/ helps. Agree with the rest but some experimental notebooks are useful to track/version control.

It's not focused on collaboration, but it does add some critical pieces that otherwise make Jupyter development frustrating when working with a team. Specifically: `nbdev_prepare` ensures that diffs are as small as possible, by removing and standardising notebook metadata; and `nbdev_fix` fixes merge conflicts so that they are cell-level, rather than line level, so they can be opened and fixed in notebooks.

Something else we've found helpful for collaboration (not associated - just happy users) is this: https://www.reviewnb.com/ . It means we can get a nice notebook-based PR workflow.

Real-time collaboration is available in Jupyter nowadays: https://jupyterlab.readthedocs.io/en/stable/user/rtc.html . nbdev doesn't have any extra functionality for it, however -- but it should work fine in this environment.

Where are you getting "mise uses asdf" from? mise is simply compatible with all asdf plugins. Not the same thing.

It's even said almost at the top of the README.md in the "30 seconds demo" section:

"The following shows using mise to install different versions of node. Note that calling which node gives us a real path to node, not a shim."

https://github.com/jdx/mise?tab=readme-ov-file#30-second-dem...

So yes, mise does not use shims. It only manipulates $PATH. I did benchmarks a while ago and that definitely and consistently has shaved some milliseconds off of the startup times of my tools.

mise borrows the plugins from asdf, which also makes it non-cross platform. Interesting discussion on this topic on their GitHub: https://github.com/jdx/mise/discussions/66

Solutions considered include adopting the vfox plugin system or transpiling all asdf plugins to ShellJs.

Now I know that vfox exists.

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

direnv + mise does exactly that. When I cd to various directories I get different env vars, it's pretty neat. Setting aliases would just be a case of adding them.

https://github.com/jdx/mise/discussions/1525 for an example of how I use direnv with mise.

https://mise.jdx.dev/direnv.html

https://mise.jdx.dev/templates.html

Installed bun js runtime (I used mise, btw)

Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools.

It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).