The Jupyter+Git problem is now solved

Re:The Jupyter+Git problem is now solved by taeric on Wednesday July 19, 2023 @10:49AM (#36787346)

I like json for data exchange, but I will never be able to endorse the notebook is a json document idea. It is the poster child for why you would want a document markup language, and they said "why not encode it in a textual data language instead?"

Yes, even in a document model, merge conflicts can give you invalid documents. Programmers deal with this every day when they create invalid programs. Trying to hide the document into data complicates that in ways that are obvious in hindsight, and not that surprising with foresight.

[ Parent | on HN ]

Re:The Jupyter+Git problem is now solved by mistertoolbox on Wednesday July 19, 2023 @11:32AM (#36788086)

Totally agree with this. I like the Markdown subset approach LiveBook (https://livebook.dev/) has taken to play nicely with version control in comparison.

[ Parent | on HN ]

Re:The Jupyter+Git problem is now solved by pphysch on Wednesday July 19, 2023 @11:30AM (#36788046)

I suspect that .ipynb will eventually be displaced by good old HTML documents loading PyScript (or more specifically, a notebook framework built on PyScript).

[ Parent | on HN ]

Re:The Jupyter+Git problem is now solved by cxr on Wednesday July 19, 2023 @05:31PM (#36793737)

Imagine if the browser makers could be convinced to add native support for a scripting language (doesn't necessarily need to be Python-related). Then you wouldn't even need to use a dedicated notebook application (or ask the people you're sharing with to download one) to author and/or run your notebooks. You could just give anyone the file and they could open it anywhere.

[ Parent | on HN ]