3 ms·
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 docume
by taeric 3y ago
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.
- pphysch 3y agoI suspect that .ipynb will eventually be displaced by good old HTML documents loading PyScript (or more specifically, a notebook framework built on PyScript).
- deleted 3y ago[deleted]
- mistertoolbox 3y agoTotally agree with this. I like the Markdown subset approach LiveBook (https://livebook.dev/ https://livebook.dev/) has taken to play nicely with version control in comparison.