3 ms·
As a potential user, I am quite unsure as to why I would use this over something like TexStudio or even VSCode enabled with some LaTeX plugins. Could you tell m
by vaastav 5y ago
As a potential user, I am quite unsure as to why I would use this over something like TexStudio or even VSCode enabled with some LaTeX plugins. Could you tell me/us some pro/cons of this?
- vinni2 5y agoMay be you could host it like overleaf? Eliminates the need to install latex which can be quite space consuming.
- adornedCupcake 5y agoUsing texlive package manager plus a python auto-package installer wrapper for latexmk I was able to get my latex install down to a 300MB.
- williamstein 5y agoI am the co-author of a very similar application (CoCalc for LaTeX) and our landing page https://cocalc.com/doc/latex-editor.html https://cocalc.com/doc/latex-editor.html lists many of the reasons people use it. A number of the reasons apply also to JupyterLab LaTeX, or will soon. A quick summary: realtime collaboration, having the paper you're writing and the data you're computing in the same place, having a very high-resolution history of edits, using latex in course management, using a Chromebook or other lightweight client, and zero configuration support for PythonTex and R (knitr). Note that some of these reasons for using JupyterLab or CoCalc are things that https://www.overleaf.com/ https://www.overleaf.com/ doesn't provide.
- harles 5y agoHaving your data and your reports all in one place seems like the big selling point and I see this as pretty exciting.
- mrlatinos 5y ago> realtime collaboration, ... having a very high-resolution history of edits It's my understanding that JupyterLab doesn't support concurrent editing or version control, unless these are baked into this extension?
- jdnier 5y agoSame here. It's the most painful limitation of Jupyter, in my experience.
- williamstein 5y agoComing soon - they just closed their concurrent editing ticket! :-). https://github.com/jupyterlab/jupyterlab/issues/5382#event-4742301847 https://github.com/jupyterlab/jupyterlab/issues/5382#event-4...