Show HN: Inlyne, a GPU powered, browser-less, Markdown previewer

Re:Show HN: Inlyne, a GPU powered, browser-less, Markdown pr... by SahAssar on Monday August 22, 2022 @11:21AM (#32552726)

Most graphical markdown renderers seems to convert markdown to html and then render that html using a browser engine. This includes basically any based on electron (vscode, atom, obsidian, roam) and a lot of others that do it via platform web views.

The point of the browser-less claim is that it converts the md to html the same way most existing engines do, but then does not use a browser engine to render it, instead using something faster and more purpose-built.

As for the GPU-thing I'm not sure, but for example terminals are sometimes written to take advantage of GPU's (kitty for example: https://sw.kovidgoyal.net/kitty/#design-philosophy ) so why not this?

[ Parent | on HN ]

Re:Show HN: Inlyne, a GPU powered, browser-less, Markdown pr... by imran0 on Tuesday August 23, 2022 @08:56AM (#32564213)

Something like a simple markdown renderer has little reason to use the GPU. But a terminal emulator has absolutely no reason to use one. The bottlenecks there are system I/O and legacy API's, not the rendering performance.

[ Parent | on HN ]

Re:Show HN: Inlyne, a GPU powered, browser-less, Markdown pr... by trimental on Tuesday August 23, 2022 @03:15PM (#32569860)

The terminal statement is false. In fact I contributed an Alacritty feature that stopped rendering when the window was occluded that cut CPU usage from ~10% to ~0.4% when not visible. There's also a misconception on what GPU's are useful for. Being the graphics processing unit they are much faster for processing images and glyph graphics then the cpu.

[ Parent | on HN ]