neatroff VS Electron

I recommend sticking with Groff. There are other implementations of Troff—some older (Heirloom Doctools), some newer (Neatroff)—but most of the documents you'll encounter in the wild will have been written with Groff in mind.

Plan 9 troff might work! It works with utf8 out of the box[0], and while I haven't used it for complex math typesetting, there is a command (eqn [1]) that was developed for it. I'd recommend Ali Rudi's port (neatroff [2][3]) for a minimalist implementation. There's also Heirloom Documentation Tools [4] which is an implementation of *roff-and-friends that uses Knuth's paragraph-at-once algorithm (instead of the original line-wise one) for typesetting, plus some other interesting features.

The authors of eqn wrote a paper about it: "Typesetting Mathematics" by Brian Kernighan and Lorinda Cherry. Kernighan also wrote two manuals (one in 1976 with a revision in 1992, and one in 2007 with updates for the Plan 9 version). [5].

[0] utf8 was developed by Ken Thompson and Rob Pike during the creation of Plan9. The entire OS is compatible. Story here: http://doc.cat-v.org/bell_labs/utf-8_history

[1] http://man.cat-v.org/plan_9/1/eqn

[2] https://github.com/aligrudi/neatroff

[3] PDF manual for neatroff: http://litcave.rudi.ir/neatroff.pdf

[4] https://n-t-roff.github.io/heirloom/doctools.html

[5] These (and more) can be found here: http://www.kohala.com/start/troff/troff.html

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