ShareLaTex VS draw.io

I guess this is a competitor to services such as overleaf [1] and codimd [2]. Although this is yet another syntax, it seems to be supported by pandoc [3]. Lately, I have been using Quarto [4] more and more as I program in R, which also produces very nice outputs, especially HTML. But none of these solve the academic usage problems of (1) producing nice diffs for reviewers, and (2) can easily be shared with, and commented by, non-technical collaborators. Thus, I fear Word will be difficult to replace for many years, at least in my field, for scientific writing

[1] https://github.com/overleaf/overleaf

[2] https://github.com/hackmdio/codimd

[3] https://pandoc.org/typst-property-output.html

[4] https://quarto.org/

Looking at the commits history[1], they are very probably using something else than (public) GitHub for many Pull Requests. On Friday, there were 7 pull requests merge and more commits referencing merge requests not available on GitHub.

[1] https://github.com/overleaf/overleaf/commits/main/

you can already self host it https://github.com/overleaf/overleaf

Mostly open source... Here's the repo: https://github.com/overleaf/overleaf. But you can see what features are only available in the paid versions here

Overleaf's license. I highly suggest reading point 10. I only skimmed it, but there are probably other pertinent details.

Look at the project license: https://github.com/overleaf/overleaf/blob/main/LICENSE

> The diagrams in particular are very clear. (They seem to have been done in draw.io: https://github.com/8dcc/8dcc.github.io/blob/main/img/pool-al... which seems to be a pretty decent Apache-2.0 free software licensed diagram editor: https://github.com/jgraph/drawio/)

Yes, this is true. Furthermore, the diagram information for draw.io is included in the SVG images themselves, so one could edit them there.

> It says, "The pool allocator, however, is much faster than malloc", but doesn't provide any benchmarks or even an order of magnitude.

You are right, I was referring to "malloc-like" allocators (i.e. for variable-size blocks). It would be a good idea to benchmark them.

It would be perfect if the symbols I wanted were already built in. There are some electrical symbols but they're very much circuit design focused whereas I'm looking for symbols such as these https://www.edrawmax.com/templates/1011842/

Additionally, https://github.com/jgraph/drawio/issues/1660 would be a nice to have.

Its been a while since I've been editing diagrams outside of a codebase; and today I hit this issue.

Thinking it was a small, transitory issue, it appears one of the most useful webapps has been getting the good old runaround from Google since March (https://github.com/jgraph/drawio/issues/4212).

Draw.io (diagrams.net)

At first I thought this was drawio: https://www.drawio.com/ with which you can generate a schema diagram from SQL. Is this the other way around.

For anyone who is willing to use a webapp, I like drawio[0]. You can download locally[1] and self host (I just use the python webserver).

While finding the Github, I see they now actually package an Electron application, so that is probably worth exploring[2].

[0] https://www.drawio.com/

[1] https://github.com/jgraph/drawio

[2] https://github.com/jgraph/drawio-desktop