Re:JupyterLab Desktop App now available
by gobookdev on Wednesday September 22, 2021 @07:56PM
(#28623592)
I use VS Code notebooks a lot, I like the workflow so much that I made an extension for Go called gobook using the API. I bind everything notebook related to shift+alt, so shift+alt+enter to run cell, shift+alt+r to run all etc. I'm learning Rust and working on a VS Code notebook for it now.
Re:JupyterLab Desktop App now available
by AlexanderTheGr8 on Wednesday September 22, 2021 @11:25PM
(#28624918)
A notebook for Rust? How does that work? I thought notebooks can only be used for interpreted language and not for compiled ones...
Re:JupyterLab Desktop App now available
by msdrigg on Thursday September 23, 2021 @01:14AM
(#28625409)
Theres a repl for rust that can be used in a Jupyter notebook. I am also curious about how it works under the hood but here it is for anyone to check out: https://github.com/google/evcxr
Re:JupyterLab Desktop App now available
by gobookdev on Wednesday September 22, 2021 @11:29PM
(#28624933)
The way I did it for Go was by having a API start up on the local machine that executes the code and returns the result to VS Code, going to do the same for Rust.
Re:JupyterLab Desktop App now available
by minimaxir on Wednesday September 22, 2021 @05:58PM
(#28622492)
> Also - and this is the deal breaker for most people I know - you can't display graphs within your notebook. Until we get that ability - everyone I know who does work and lives off of their matplotlib workstream is going to continue using Jupyter Lab/Notebooks.
Hmm? The latest demos seem to imply that a plt.show() does embed the plot images into the Notebook.
The major limit on cell outputs is more limited interactivity.
Re:JupyterLab Desktop App now available
by gobookdev on Wednesday September 22, 2021 @08:24PM
(#28623812)
The API microsoft provides allow you to make outputs that do anything that JavaScript can do, when making an extension. One of their engineers made a something called REST Book that's a really good example.
What I love about VS Code Notebooks - it's almost zero context switching to jump from the the code you are working on to a REPL and back.
What I don't love about VS Code Notebooks (and why I still spend a lot of time in JupyterLab) - the context gets confused as to what cell you are in frequently - so your Ctrl-Enter keys don't work, and you have to manually run each cell one at a time.
~Removed comment about graphs not being inline~ - I stand corrected. Just checked an the latest version does let you show your graphs inline. And they look awesome.