I strongly agree with the premise of the article - HTML could be a fabulous substrate for computational notebooks!<p>But I didn't love the choices for how to implement it here. Dynamic, reactive HTML can be a lot more declarative than this, and Observable is cool, but strays from standard JS.<p>I started to build a reactive HTML system called Heximal that eventually will have notebook support, but it's declarative, based on HTML templates and custom elements with a expression / reactivity system (based on the TC39 Signals proposal) on top.<p><a href="https://github.com/elematic/heximal">https://github.com/elematic/heximal</a><p>It's a bit like a mashup of HTMX, Tangle, Curvenote, and Polymer. Or like HTML if were natively reactive.<p>I think it will lend it self to graphical editing and notebook user cases quite well.
Really cool! I particularly liked your Python and SQLite demos. I find it interesting that you <i>started</i> with a through-the-web (TTW) editing loop, calling it a quine. While valid, the key weakness is persistance: TidlyWiki does basically the same thing, but saving your work is a headache because basically you need another headless server process to persist anything.<p>Personally, when wanting to do something similar[0], started with persistance, and of course this means files. Plain text files I can edit with my programmer's editor store and distribute using the file-system. This avoids the problem of having to recapitulate a programmers editor in the browser, which is non-trivial. In turn you have the problem of writing a fast server, but that is a rather fun problem to solve [1]. You side-stepped the problem by using basic content-editable sections, but it is a huge problem, second only to persistence.<p>One thing I see you face which I also faced is the fact you cannot export things from inside embedded scripts! This would be a nice feature to avoid mangling the global window object. (It would also, in my use case, make code generation easier.)<p>0 - Literate Markdown: <a href="https://simpatico.io/lit.md" rel="nofollow">https://simpatico.io/lit.md</a><p>1 - Reflector, what I call the small node server that transforms, zips and caches your markdown, with a filewatcher invalidator: <a href="https://simpatico.io/reflector" rel="nofollow">https://simpatico.io/reflector</a>
With all due respect to the considerable thought and effort you put into this, the ergonomics of this approach are hideous. Why would I ever care about the styling elements when I'm just trying to do some exploratory data analysis. This is exactly why things like Jupyter notebooks excel. Regardless kudos to your curiosity and implementing alternate ideas.
The original author of Lit recently left Google and is working on something very similar to this AFAIK.<p><a href="https://github.com/elematic/heximal">https://github.com/elematic/heximal</a>
I enjoy the format of this post. Work from ground up to something interesting. Not tons of dependencies and framework here framework there blablabla hype.<p>To follow along it seems you can just copy paste the given snippets and understand step by step how it works. If I wrote something like this, I guess I would use literate programming in org-mode and export to HTML, to make it a blog post.<p>I still question fonts with built-in syntax highlighting.
I will soon make attempts to support this kind of HTML notebook in/for Raku.
Right now Raku's "notebook solutions" are Jupyter-based or Mathematica-based.
I don't get the argument for using web technologies to complicate this process. What does this added complexity solve? If anything, it slows the process and remove much needed features like auto-completions, snippets, and extensions. Also, it makes collaboration harder, since, most likely, others aren't familiar with your setup.<p>You only need to setup one environment once and use it forever with minor incremental improvements as tech evolves.<p>If you are a n/vim user, you can accomplish this by:<p>1- Data exploration: text -> jupyter notebook via <a href="https://github.com/untitled-ai/jupyter_ascending">https://github.com/untitled-ai/jupyter_ascending</a> that uses jupytext. This way, you can efficiently edit and run code from your text editor.<p>2- Writing: you can use <a href="https://github.com/lervag/vimtex">https://github.com/lervag/vimtex</a> for LaTeX<p>On top of these, you can use tmux with tmuxp to open projects instantly.<p>You can have a seamless process with Emacs using org mode [1] [2] and/or Auctex.<p>[1] <a href="https://sqrtminusone.xyz/posts/2021-05-01-org-python/" rel="nofollow">https://sqrtminusone.xyz/posts/2021-05-01-org-python/</a><p>[2] <a href="https://martibosch.github.io/jupyter-emacs-universe/" rel="nofollow">https://martibosch.github.io/jupyter-emacs-universe/</a>
I tend to agree with the premise of this article -- that [HTML is underutilized as a medium for disseminating scientific writing].<p>Some recent work related to this done by Will Crichton:<p><a href="https://willcrichton.net/nota/" rel="nofollow">https://willcrichton.net/nota/</a>
<a href="https://willcrichton.net/notes/portable-epubs/" rel="nofollow">https://willcrichton.net/notes/portable-epubs/</a>
Notebooks are hot these days! We also shipped our own version of a TypeScript notebook[1] but it takes quite different sides of the tradeoff: we want to run backend node code, so unlike this or observable we're not looking to run in the browser environment. Still, for many applications, this idea is a better take!<p>Kudos to the author.<p><a href="https://github.com/srcbookdev/srcbook">https://github.com/srcbookdev/srcbook</a>
First of all, incredible. This is right up my alley.<p>I tried editing the pyodide one (which rendered fine before editing) on my phone (iphone 13 + brave) and it crashed and reloaded the page.
This is awesome - I have been toying with building something like this so that i can host (raku) code examples and do literate programming. FWIW there IS a good raku plugin for Jupyter Chatbooks (<a href="https://raku.land/zef:antononcube/Jupyter::Chatbook" rel="nofollow">https://raku.land/zef:antononcube/Jupyter::Chatbook</a>), but it just seems kinda wrong for raku to need python to do this.<p>Can this example be widened to use server side code (I am not too bothered about syntax highlighting as maybe can make a font for that) - but it would be great to have some kind of message layer (like zmq in Jupyter) to connect to a remote language kernel perhaps using web sockets???<p>Raku does not (yet) target wasm so that option is out.
Awesome work. Thank you for sharing. Yes, web technologies coming with web browsers, HTML, CSS, DOM, JAVASCRIPT, PHP, .., can be used directly inside web browsers. This is how I use them to build a tiny web text editor coming with a programming language : <a href="http://lambdaway.fr" rel="nofollow">http://lambdaway.fr</a> . Your opinion would be appreciated.
The article was a great read! I wonder if you know about marimo.io; it's an open-source reactive notebook for Python which offers tons of great features. I have shifted my daily notebook usage (from what used to be colab and jupyter notebooks) to marimo notebooks over the past months.
Awesome implementation!<p>> 3. Export to .pdf for distribution<p>I was certain you were using something like <a href="https://pagedjs.org" rel="nofollow">https://pagedjs.org</a> or <a href="https://printcss.net" rel="nofollow">https://printcss.net</a> for the PDF export, but its just the SydJS or am I missing something?