3 ms·
I would be surprised, if Impeller isn't eventually ported to the web, as it's much smaller (100KB per architecture) than Skia/CanvasKit (1.5 MB). But like you s
by zigzag312 2y ago
I would be surprised, if Impeller isn't eventually ported to the web, as it's much smaller (100KB per architecture) than Skia/CanvasKit (1.5 MB). But like you said, this won't happen any time soon.
Note that size comparison is not completely fair as even with Impeller, Skia (as HarfBuzz is embedded into it) is still used for text layout and shaping.
> Updating the web engine to interface directly with Impeller is a non-goal at this time. It is a significant undertaking (compared to a flag to swap dispatchers that already exists) and also bypasses display list optimizations.
> For this added implementation complexity, Web support has not been a priority at this time for the small team working on Impeller.
> 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/faq.md https://github.com/flutter/engine/blob/main/impeller/docs/fa...
- nmfisher 2y agoYes, you're probably right. I believe (?) the intention is also to publish Impeller as a standalone rendering engine (i.e. independent of Flutter). Will be interesting to see if there's a use case there too.