I&#x27;ve been using GV for coming up on a decade and it has the same problem that Dia has - you can tell it was made by engineers. In the same way you can look at code written by a UX guy and just <i>know</i> it wasn&#x27;t written by someone formally educated in CS, the converse applies when engineers try to do UI.* Engineers historically just cared about the functionality - e.g., &quot;Does this UML depict the information as precisely as possible? OK. Good. Next problem.&quot;<p>You saw the same problems with XFree86 WM&#x2F;DEs. I spent <i>months</i> trying to get XFCE to be perfect in the late &#x27;00s, but it just always looked <i>off</i>. I&#x27;m a keyboard-consoler 98% of the time anyways, so staying in my `screen&#x27; instance was fine (in fact preferable,)with a nicely configured Konsole (or was it aterm, or did E17 have it&#x27;s own Term? One of those..) full-screened. But such is the folly of projects like DIA and GV. It&#x27;s getting better as NYT and all end up hiring people who have multi-disciplinarian abilities (I think Square or AirBNB open-sourced their dashboard which has a lot of good vis tools) but I really just want a standard, declarative language I can embed in Pandoc that looks good whether I export to PDF, HTML or print it.<p>*LaTeX not withstanding. Knuth brilliantly applied mathematical rules to typesetting and I maintain it still beats out InDesign in certain scenarios, granted I&#x27;ve heard many-a-grad-student&#x27;s yells of frustration as they try to embed their results into a .tex, so YMMV. Look at this TeX and I defy anyone to tell me it&#x27;s not pretty:
<a href="https:&#x2F;&#x2F;bloerg.net&#x2F;2014&#x2F;09&#x2F;20&#x2F;a-modern-beamer-theme.html" rel="nofollow">https:&#x2F;&#x2F;bloerg.net&#x2F;2014&#x2F;09&#x2F;20&#x2F;a-modern-beamer-theme.html</a>