4 ms·

You absolutely can use regular jupyter notebooks for julia! Pluto has some advantages, like being stored as a normal julia file. The julia startup time issues a

You absolutely can use regular jupyter notebooks for julia! Pluto has some advantages, like being stored as a normal julia file. The julia startup time issues affect both.

enriquto 6y ago
> being stored as a normal julia file. Oh, man, this is indeed a major feature. My main point of friction with jupyter notebooks is the stupid json ipynb format. Why can't it be just a regular language file with comments?
- goerz 6y ago
  Sounds like you want jupytext
  - enriquto 6y ago
    Yes. What I really want is that ipynb disappears everywhere forever to be replaced by jupytext or a variant of it.
- Jugurtha 6y ago
  >My main point of friction with jupyter notebooks is the stupid json ipynb format. Why can't it be just a regular language file with comments? Have you ever used Jupyter notebooks? They contain code, rendered Markdown, images, plots, video players, widgets, etc. How do you see a "regular language file with comments" supporting this, instead of the "stupid ipynb format"? You can use plain text files with Jupyter, too.
  - enriquto 6y ago
    > They contain code, rendered Markdown, images, plots, video players, widgets, etc. The code could be verbatim python code (or whatever language the notebook uses), and the rest could be embedded inside comments. I don't see any problem with that (besides the very concept of "rendered Markdown" being totally out of order). The fact that they are saving it as json by default seems more to be laziness by the developers than a well thought-out solution, that could be just a straightforward serializer.
    - Jugurtha 6y ago
      >and the rest could be embedded inside comments. I don't see any problem with that Do you mean embedding images and plots inside comments? If yes, please elaborate on how you see that happening in the real world. >The fact that they are saving it as json by default seems more to be laziness by the developers than a well thought-out solution, that could be just a straightforward serializer. So, how would that well thought-out solution in the form of a "straightforward serializer" work? I have a flat file, and I want to display images, plots that you can zoom into out of, figures, etc. as comments. How would that happen?
      - enriquto 6y ago
        > How would that happen? At the very least, you could put the whole json stuff inside a comment. It's already plain text, isn't it?
        Jugurtha 6y ago
        >At the very least, you could put the whole json stuff inside a comment. It's already plain text, isn't it? So instead of having the whole file as JSON, which is lazy and not well thought-out, we'll put all content in JSON, then put that JSON inside a comment in a plain text file. Do I read you correctly? I feel we're making progress faster than these lazy Jupyter org bandits.
        enriquto 6y ago
        > we'll put all content in JSON, then put that JSON inside a comment in a plain text file Only the "output" content. The code inside the cells is verbatim, and the markdwon cells are regular text comments. See, I'm not discussing you just because. I have a legitimate problem with ipynb: very often I want to run the code of a notebook from the command line, or import it from another python program. This is quite cumbersome with the ipynb, but it would be trivial if it was a simple program with comments.
        Jugurtha 6y ago
  - ulucs 6y ago
    Rmarkdown does this perfectly

You absolutely can use regular jupyter notebooks for julia! Pluto has some advantages, like being stored as a normal julia file. The julia startup time issues affect both.

enriquto 6y ago

> being stored as a normal julia file. Oh, man, this is indeed a major feature. My main point of friction with jupyter notebooks is the stupid json ipynb format. Why can't it be just a regular language file with comments?

goerz 6y ago
Sounds like you want jupytext
- enriquto 6y ago
  Yes. What I really want is that ipynb disappears everywhere forever to be replaced by jupytext or a variant of it.
Jugurtha 6y ago
>My main point of friction with jupyter notebooks is the stupid json ipynb format. Why can't it be just a regular language file with comments? Have you ever used Jupyter notebooks? They contain code, rendered Markdown, images, plots, video players, widgets, etc. How do you see a "regular language file with comments" supporting this, instead of the "stupid ipynb format"? You can use plain text files with Jupyter, too.
- enriquto 6y ago
  > They contain code, rendered Markdown, images, plots, video players, widgets, etc. The code could be verbatim python code (or whatever language the notebook uses), and the rest could be embedded inside comments. I don't see any problem with that (besides the very concept of "rendered Markdown" being totally out of order). The fact that they are saving it as json by default seems more to be laziness by the developers than a well thought-out solution, that could be just a straightforward serializer.
  - Jugurtha 6y ago
    >and the rest could be embedded inside comments. I don't see any problem with that Do you mean embedding images and plots inside comments? If yes, please elaborate on how you see that happening in the real world. >The fact that they are saving it as json by default seems more to be laziness by the developers than a well thought-out solution, that could be just a straightforward serializer. So, how would that well thought-out solution in the form of a "straightforward serializer" work? I have a flat file, and I want to display images, plots that you can zoom into out of, figures, etc. as comments. How would that happen?
    - enriquto 6y ago
      > How would that happen? At the very least, you could put the whole json stuff inside a comment. It's already plain text, isn't it?
      - Jugurtha 6y ago
        >At the very least, you could put the whole json stuff inside a comment. It's already plain text, isn't it? So instead of having the whole file as JSON, which is lazy and not well thought-out, we'll put all content in JSON, then put that JSON inside a comment in a plain text file. Do I read you correctly? I feel we're making progress faster than these lazy Jupyter org bandits.
        enriquto 6y ago
        > we'll put all content in JSON, then put that JSON inside a comment in a plain text file Only the "output" content. The code inside the cells is verbatim, and the markdwon cells are regular text comments. See, I'm not discussing you just because. I have a legitimate problem with ipynb: very often I want to run the code of a notebook from the command line, or import it from another python program. This is quite cumbersome with the ipynb, but it would be trivial if it was a simple program with comments.
        Jugurtha 6y ago
- ulucs 6y ago
  Rmarkdown does this perfectly