pathfinder VS svgbobrus

https://github.com/coconut-xr/apfel-kruemel works today, I only know about battery-optimized software in the context of games though.

https://felt.com/blog/svg-to-canvas-part-2-building-interact... and https://github.com/servo/pathfinder/ might also be of interest.

Parts of Servo to enable the use of the GPU for compositing layers were merged into Firefox years ago.

https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-f...

It's a shame that Patrick Walton didn't get a chance to finish his work on the Pathfinder GPU renderer.

>Pathfinder 3 is a fast, practical, GPU-based rasterizer for fonts and vector graphics using OpenGL 3.0+, OpenGL ES 3.0+, WebGL 2, and Metal.

https://github.com/servo/pathfinder

You might be interested in https://github.com/servo/pathfinder

It uses too much CPU and performance leaves much to be desired compared to Chromium. They were going to use Pathfinder in Firefox to solve this problem, but since Pathfinder is discontinued due to the massive layoffs at Mozilla, the project was abandoned. And they need a replacement IMO.

I am not an expert in the area, just somebody who read up on it after realizing desktop in VR does not work out for me (and usually low res is not a problem).

I think something like https://github.com/servo/pathfinder (newer) and as you mentioned SDF (older) are the latest approaches.

This is exciting! And, by the way, are you planning to implement something similar to Servo's Pathfinder in Firefox?

Also on my list was pathfinder. There the documented crate is vastly different from https://github.com/servo/pathfinder which looks much more promising – it comes with a few examples, some of wihch might help me get started, maybe?

Have you checked out the Pathfinder library?

https://github.com/servo/pathfinder

Don't forget gpu-based text rendering (e.g. #1, #2, #3). It's still in its infant stages, and seems to be mostly untouched over the past 5 years, but I suspect it will become the preferred method for rendering text later.

I recently had to draw some diagrams for documenting something. After looking at various Markdown-friendly options I landed on svgbob[1]. I believe it's a superior solution to these kinds of graph drawing tools for Markdown for one specific reason: the code is still readable. When I go to look at a Markdown file I don't always open the output. I will commonly open up a README file in Vim or just cat it to the terminal. In this case diagrams like those in this post is next to useless. I'm not going to read through some complex drawing definitions and try to visualise the results. With svgbob (or Typograms[2] or any of the other similar options) you can still read the Markdown text document and see the diagrams which is great!

Of course this comes with a tradeoff, drawing the diagrams can be a bit of a pain. But I believe this can be solved by a good Markdown editor or editor plugin. Alternatively a spec like this could be converted into an svgbob-compatible diagram.

[1]https://ivanceras.github.io/svgbob-editor/

Online playground svgbob-editor is also updated to use the latest version of svgbob. It is however a painfully slow to edit the diagrams from there, so it's better if you draw the diagram somwhere else and paste it to there.

There’s Svgbob. Plus when it comes to more complex diagrams or graphs where creating the ASCII art by hand in can be quite finicky, there’s a number of tools (including drawing tools) to make creating ASCII art much easier.

https://ivanceras.github.io/svgbob-editor/

svgbob

Since the post contains ASCII art, let me recommend you svgbob :)

The app can now render Svgbob code blocks (https://ivanceras.github.io/svgbob-editor).