engine VS angle

Impeller - Flutter’s rendering library that replaces Skia on iOS and Android - is working on a C API: https://github.com/flutter/engine/blob/main/impeller/toolkit...

https://github.com/flutter/engine/graphs/contributors

We are aware that these priorities might change in the future. There have been sanity checks to ensure that the Impeller API can be ported to WASM and also that Impeller shaders can be compiled to WGSL for eventual WebGPU support.

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

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.

https://github.com/google/angle

ANGLE is the de-facto standard library that all of the big browsers use to implement WebGL on top of other graphics APIs, if you want to read up on it.

If you want OpenGL use ANGLE

https://github.com/google/angle

several phones now ship ANGLE as their only OpenGL support on top of their Vulkan drivers.

If you want a modern-ish API that's relatively easy and portable use WebGPU via wgpu (rust) or dawn (c++).

It's using MoltenVK on Mac for Vulkan compatibility, and ANGLE for OpenGL compatibility on Windows and Linux. Makes you wonder what it's actually doing itself.

Can't they use https://github.com/google/angle?

BTW. For the last 15 years, all web browsers on Windows do WebGL on top of DirectX (using the Angle library https://github.com/google/angle).

You can still use OpenGL. Just not the vendor provided drivers. They are indeed horrible. There are libraries like:

* ANGLE ( https://github.com/google/angle ) - An OpenGL ES implementation with Direct3D 9, Direct3D 11, Desktop GL, GL ES, Vulkan and Metal backends. This is what we used to use for shipping our Qt 3D application, that used a bunch of OpenGL Shaders. We used to get bug reports about various shaders not working properly on various hardware. After switching to this, all those bug reports vanished.

* Zinc ( https://www.supergoodcode.com/do-not/ ) - A more recent, OpenGL implementation on top of Vulkan. I haven't used this one yet. But they are making a lot of progress and it is almost as performant as vendor provided OpenGL Drivers these days. So if I ever have to ship a desktop app, needing opengl, I'd strongly consider using this.

Another option if perf isn't a big concern is to try using Google's angle OpenGL ES 3.0 implementation, there's backends for it to be supported on Vulkan, Direct3D 11, and (work in progress) Metal. Disclosure, haven't tried it myself, just looking at their feature descriptions: https://github.com/google/angle