Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JupyterLite: a JupyterLab distribution that runs in the browser

github.com

Post reply on HN
Print view View original

51–58 of 58 posts

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#51

Post by kmacdough »

e12e wrote: post #50
SilverBirch wrote: post #41

Earlier quoted context omitted.

While this is obviously a great demonstration as to why you wouldn't do something silly like build an entire code editor in the browser for day to day use (because it would be slow and clunky and have all sorts of issues), it's great for a accessibility when you don't need performance at all.

Is this a snide comment on Atom and VS code? (I do think they're "slow" but not necessarily more than non-web rich IDEs - just compared to something like vim with conservative config/plug-ins).

I don't think so.

VSCode, Atom (and Jupyter) all run natively, only using a browser renderer for UI.

Jupiter already uses a browser as the front end, but the kernel runs natively.

JupiterLite runs entirely in the browswer, including the kernel. This means you don't need Jupyter installed or running on a server to execute the kernel. But it also means the kernel is running much slower in Web Assembly.

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#52

Post by protoduction »

abdullahkhalids wrote: post #31
yewenjie wrote: post #16

Earlier quoted context omitted.

I love the idea of Starboard. But seems like the development has stalled?

Yes. Last commit was 5 months ago [1]. Seems like a great idea though. What I don't like it is that they invented yet another markdown syntax for code cells - it is the opening bracket # %[python] with no closing bracket. There already is a popular markdown code cell syntax of [2] ```python ``` [1] https://github.com/gzuidhof/starboard-notebook [2] https://github.github.com/gfm/#fenced-code-blocks

The format is only partially invented, it follows Jupytext [0], but adds support for cell metadata. There is no obvious way to get that in fenced codeblocks, especially with the ability to spread it over multiple lines so it plays well with version control.

One more consideration is that it's not "Markdown with code blocks interspersed", one might as well use plaintext or AsciiDoc.

Of course there are tradeoffs.. I wish I had more time to work on it.

[0]: https://github.com/gzuidhof/starboard-notebook/blob/master/d...

[1]: https://github.com/mwouts/jupytext

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#53

Post by abdullahkhalids »

protoduction wrote: post #52
abdullahkhalids wrote: post #31

Earlier quoted context omitted.

Yes. Last commit was 5 months ago [1]. Seems like a great idea though. What I don't like it is that they invented yet another markdown syntax for code cells - it is the opening bracket # %[python] with no closing bracket. There already is a popular markdown code cell syntax of [2] ```python ``` [1] https://github.com/gzuidhof/starboard-notebook [2] https://github.github.com/gfm/#fenced-code-blocks

The format is only partially invented, it follows Jupytext [0], but adds support for cell metadata. There is no obvious way to get that in fenced codeblocks, especially with the ability to spread it over multiple lines so it plays well with version control. One more consideration is that it's not "Markdown with code blocks interspersed", one might as well use plaintext or AsciiDoc. Of course there are tradeoffs.. I w…

Thanks for the clarifications. I still don't like it, but I understand.

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#54

Post by SilverBirch »

e12e wrote: post #50
SilverBirch wrote: post #41

Earlier quoted context omitted.

While this is obviously a great demonstration as to why you wouldn't do something silly like build an entire code editor in the browser for day to day use (because it would be slow and clunky and have all sorts of issues), it's great for a accessibility when you don't need performance at all.

Is this a snide comment on Atom and VS code? (I do think they're "slow" but not necessarily more than non-web rich IDEs - just compared to something like vim with conservative config/plug-ins).

Yeah I’ve had a slowly bubbling level of hatred towards vscode for the last few months. Because it’s heft it’s absorbed all the plug-in ecosystem but it’s like sublime text left the sunroof open and now everything is soggy.

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#55

Post by cyanydeez »

SilverBirch wrote: post #54
e12e wrote: post #50

Earlier quoted context omitted.

Is this a snide comment on Atom and VS code? (I do think they're "slow" but not necessarily more than non-web rich IDEs - just compared to something like vim with conservative config/plug-ins).

Yeah I’ve had a slowly bubbling level of hatred towards vscode for the last few months. Because it’s heft it’s absorbed all the plug-in ecosystem but it’s like sublime text left the sunroof open and now everything is soggy.

There's definitely a noticeable input lag in vscode.

I basically nerfed the vscode language features which make it more manageable.

But sublime still feels far more responsive.

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#56

Post by Y_Y »

martinRenou1 wrote: post #45
Y_Y wrote: post #43

Whatever happened to collaborative editing in these notebooks? It would be a great usecase for JupyterLite but last I saw the only project for real-time sharing of notebooks over the network was slurped up into Google Colab any open version was abandoned.

Oh it's happening! https://jupyterlite.readthedocs.io/en/latest/howto/configure...

Excellent news, thank you! Imagine telling someone even ten years ago that they could program something in a notebook environment, over the internet, in a slow language, with all the work of setup and computation being done in the browser, and it would still be convenient and fast!

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#57

Post by ivansavz »

abdullahkhalids wrote: post #26
tartakovsky wrote: post #9

This GitHub Actions + GitHub Pages feature looks like the use case I would be looking to exploit for educational purposes. From this: https://github.com/jupyterlite/demo you can easily get to https://jupyterlite.github.io/demo In case anyone wants to be helpful, I would love to see a guide to how to use this to transparently display where files are stored so that I could figure out how to automatically commit my chan…

Yes, the reason I posted this is because I was looking into how to host my mini-book online, which has a lot of computational interactions built in. I don't want to deal with hosting the backend on my server and all the security and performance issues it entails. This is a great solution. Though not ideal. I want to publish the book as a jupyter-book, and best would be if the code cells in it were interactive. I thin…

There was some work (and POC) on getting pyodide to work as a thebe backend. You can check out this thread: https://github.com/executablebooks/thebe/issues/465 and other issues/PRs backlinked to it. I don't think anything like that has shipped yet, but definitely worth exploring (in the meantime the usual mybinder backend[1] for jupyter books works great, i.e. you don't have to host yourself).

[1] https://jupyterbook.org/en/stable/interactive/launchbuttons....

Re: JupyterLite: a JupyterLab distribution that runs in the browser

#58

Post by ivansavz »

tartakovsky wrote: post #9

This GitHub Actions + GitHub Pages feature looks like the use case I would be looking to exploit for educational purposes. From this: https://github.com/jupyterlite/demo you can easily get to https://jupyterlite.github.io/demo In case anyone wants to be helpful, I would love to see a guide to how to use this to transparently display where files are stored so that I could figure out how to automatically commit my chan…

> I would love to see a guide to how to use this to transparently display where files are stored [...]

I'm not 100% sure I understand your request for a guide, but if you create your own repo based on the jupyterlite/demo template, you can then put your notebooks in `content` dir[1] and they will automatically become available. The CI build step that does this is here[2]. So in some sense you don't need a guide, it just works ;)

[1] https://github.com/jupyterlite/demo/tree/main/content

[2] https://github.com/jupyterlite/demo/blob/main/.github/workfl...

Post reply on HN