that's an unhelpful articulation that runs the risk of having the opposite effect from the one you want.
That would be a pity, because Quarto is really good. I haven't tried Observable yet, but in outline they have some similarities:
1. Documents written in Markdown
2. Ability to embed code blocks in the Markdown, with code executed when the document is rendered.
3. Ability to embed output of the code blocks in the rendered result (e.g. tables, charts).
4. Ability to render to multiple formats (pdf, static site, ...).
Quarto supports Python and R as languages in the code blocks (maybe more, not sure). I personally prefer it to Jupyter notebooks because the source is plain text so (1) there's a choice of editor and (2) moving between text and code blocks is seamless.
I can't say Quarto is better than Observable but it is good. It has depth from its history in RMarkdown (like rendering mathematical equations, naming & cross-referencing).
It's certainly worth consideration for anyone looking for a "code notebook" solution.
That would be a pity, because Quarto is really good. I haven't tried Observable yet, but in outline they have some similarities:
1. Documents written in Markdown
2. Ability to embed code blocks in the Markdown, with code executed when the document is rendered.
3. Ability to embed output of the code blocks in the rendered result (e.g. tables, charts).
4. Ability to render to multiple formats (pdf, static site, ...).
Quarto supports Python and R as languages in the code blocks (maybe more, not sure). I personally prefer it to Jupyter notebooks because the source is plain text so (1) there's a choice of editor and (2) moving between text and code blocks is seamless.
I can't say Quarto is better than Observable but it is good. It has depth from its history in RMarkdown (like rendering mathematical equations, naming & cross-referencing).
It's certainly worth consideration for anyone looking for a "code notebook" solution.