gpresent VS Electron

It's funny, I looked at the "Typesetting Mathematics -- User's Guide (Second Edition)" postscript document, and - at least with macOS' Preview - some big brackets are segmented (Neatroff brackets don't seem to do this, although I've seen it in other troff generated documents), and they even say this:

> Warning — square roots of tall quantities look lousy, because a root-sign big enough to cover the quantity is too dark and heavy

The solution is naturally to rewrite big roots as powers.

pic does seem close to Tikz, although I had to look in the GNU pic doco to figure out how to do colors. Even then, transparency didn't seem to be supported?

Heirloom actually looks the most useful/mature. At least the output looks pretty/someone cared enough to make the example files pretty, there's actual documentation. Limitations are still there (having to convert bitmaps to EPS?). I will say I'm at least slightly impressed by `gpresent`, which is like beamer (so for making presentations), and built-in hyphenation support.

I still don't get Neatroff. It's compatible with/implements a lot that Heirloom does, but then the font support is worse again? It's an impressive project though, the source is very readable, and RTL/LTR support. Less impressive is the lack of a license - I think it's ISC, based on a single comment, but who knows?

---

A repository and a makefile are distinctly different than an installer. Random macro packages that may or may not be on GitHub are different than `tlmgr`. Piping stuff around and having to convert images is different than just one command. GUI editors. Example documents (like https://texample.net/). That is what I mean by ecosystem.

XeTeX outputs PDFs by default (granted, via xdvipdfmx), and can also include bitmaps directly (again, granted it needs graphicx or something). All TeX stuff isn't without it's warts, and seems overly complex (pdfTeX/XeTeX/XeLaTex/LuaTeX/ConTeXt, etc). But in practice, it kinda somehow just works (until it doesn't).

[0] https://github.com/rhaberkorn/gpresent

The team at Electron have been faithfully shipping new releases almost every single month. I think they had Christmas off 🤔. This popular framework has developers writing cross-platform desktop applications using JavaScript, HTML and CSS. The latest update depreciates some process events, and added new modules, APIs, methods, and more. Read into all the changes in the Electron release notes. This month, Electron also introduced a new formal RFC process.

VS Code has been crashing at launch in Wayland since more than eight months ago:

https://github.com/electron/electron/issues/37531

So we talked a lot about the Atomic Design Principle, but you could just use that in any system and start creating. You could have Angular components, React Components, and Vue Components. But if you notice these don't easily work Everwhere. So the solution is to use Web Components because the modern browser can already understand these, and any Front-End framework can then utilize these components. You can use Electron for desktop (Slack, VSCode), PWA for both Android and iOS, and across all browsers Can I Use.

I'm noticing a significant boost in performance, crisper text, and better power savings. The only shortcoming is that the window which Figma will run on will lose its shadow. This is due to a technical limitation with frameless windows on Linux.

For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.

Electron patch for version 27: https://github.com/electron/electron/pull/39823

It does, see [0]. Fun fact: Signal desktop, which uses Electron under the hood, is running without sandbox on Linux [1][2].

[0] https://github.com/electron/electron/pull/39824

[1] https://github.com/signalapp/Signal-Desktop/issues/5195

[2] https://github.com/signalapp/Signal-Desktop/pull/4381

Turns out, there is an issue with the electron window not returning focus correctly on mac - https://github.com/electron/electron/issues/5495. The trick to solving is to treat quick capture as a screensaver. When closing, you hide it by setting the opacity to 0 and sending hide: command to the first responder.

Open since 2016! https://github.com/electron/electron/issues/8124