pathfinder VS engine

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.

https://github.com/flutter/engine/blob/main/impeller/docs/fa...

Impeller is the Skia replacement and is in full c++ that supports all platform.

It will be great if Go team can work with them(both are in Google) and make Impeller a render engine for Go.

With this no more bloated electron.js and no more Java/Swing or Qt, what a dream for the day.

Likely it's https://github.com/flutter/engine/pull/41168 that fixed it, which got cherry picked into that commit.

Depends on what you want to do. The best documentation for writing the code where the engine should run in is in this header file.

Performance on large-screen and also high-refresh rate iPads was definitely a blind spot during the preview. We've done a ton of work to plug that gap since the preview though. Framebuffer fetch for advanced blends, improvement to blur performance, and using half-precision in performance critical shaders are just some of the improvements driven by these findings.

Yes. We use ATK for accessibility. FlAccessibleNode is where SemanticsNode and friends are exposed as ATK objects.

The hardware accelerated 3D that was demoed was using Impeller Scene. Considering they were loading glb files I really hope the Flutter API has a GLES interface. It's currently marked "Experimental" and the demo they showed unfortunately doesn't have source in the same place as the other demos presented.

For example for the last point, embed Flutter in HTML pages, an important PR is recently merged: https://github.com/flutter/engine/pull/37738