JupyterLite – WASM-powered Jupyter running in the browser
1–10 of 68 posts
Re: JupyterLite – WASM-powered Jupyter running in the browser
#2I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
Re: JupyterLite – WASM-powered Jupyter running in the browser
#3Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
It has a few quirks, but works quite good for daily use.
Re: JupyterLite – WASM-powered Jupyter running in the browser
#4Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
Re: JupyterLite – WASM-powered Jupyter running in the browser
#5Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
Re: JupyterLite – WASM-powered Jupyter running in the browser
#6Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
The solution I use for local jupyter notebooks is nteract [0] which is like a standalone application that can edit/open .ipynb files. It has a few quirks, but works quite good for daily use. [0] https://nteract.io/
Re: JupyterLite – WASM-powered Jupyter running in the browser
#7Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
Isn't that not just Java all over again, but this time with JavaScript?
Re: JupyterLite – WASM-powered Jupyter running in the browser
#8Earlier quoted context omitted.
Isn't that not just Java all over again, but this time with JavaScript?
No, WASM gets compiled to native code
Think we've just got better at runtimes over time (JIT, intermediate formats etc.) and WASM was designed to be good for this rather than needed to work with an already exising bytecode
Re: JupyterLite – WASM-powered Jupyter running in the browser
#9Earlier quoted context omitted.
The solution I use for local jupyter notebooks is nteract [0] which is like a standalone application that can edit/open .ipynb files. It has a few quirks, but works quite good for daily use. [0] https://nteract.io/
What do you like about nteract over Jupyter's frontend? The website is devoid of details.
Re: JupyterLite – WASM-powered Jupyter running in the browser
#10Despite Pyolite has a miserable performance (20MB of downloads), the overall project direction is correct. I said this already 10 years ago: We don't need more cloud computing but need to empower users end devices again. Jupyter is typically operated on powerful notebooks and not on mobile devices.
The solution I use for local jupyter notebooks is nteract [0] which is like a standalone application that can edit/open .ipynb files. It has a few quirks, but works quite good for daily use. [0] https://nteract.io/
I try to work mostly with "py:percent" script files now, in the same jupyter notebook style but without saving outputs.