wgpu_glyph VS aioquic

It won't live in WebGPU itself, but I do expect to start to see more third-party libraries for text. There’s already wgpu_glyph (https://github.com/hecrj/wgpu_glyph/tree/master) which uses a glyph atlas (CPU-rendered sprite map of characters), but techniques for signed-distance field fonts have come a long way too.

I've been searching for one all day, and wgpu_glyph is the only obvious choice, but it's incompatible with Android (and in fact crashes on startup even if all you do is add it as a dependency)

One of the interesting patterns happening in Rust is io-less libraries. I'm not sure where best to link this phenomenon. It here s a open issue for an io-less quic library, from 2019, https://github.com/aiortc/aioquic/issues/4

It'd be so fracking sweet to see filesystems follow this pattern. If we could re-use the file system logic, but apply it to windows or fuse or Linux or wasm linearly-addressed-storage, that would allow such intensely cool forms of portability/reuse & bending/hacking.

for those wishing to use http3 with a Python web framework, the ASGI hypercorn[1] currently supports it.

made a Django example last week with a sample client based on the examples from aioquic[2]: https://github.com/djstein/django-http3-example

this example also includes the first pass at async Django REST Framework using adrift[3] based on these GitHub issues:

- https://github.com/encode/django-rest-framework/pull/8617

- https://github.com/encode/django-rest-framework/issues/8496

sources

[1]: https://github.com/pgjones/hypercorn

[2]: https://github.com/aiortc/aioquic

[2]: https://github.com/em1208/adrf

In your estimation where does the QUIC specification, HTTP/3 specification, WebTransport specification, aioquic QUIC and HTTP/3 implementation in Python https://github.com/aiortc/aioquic (notice the GoogleChrome/samples WebTransport sample code is described as local server "There's code for a sample local server at https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py") fit into the categories you color "Framework" and "Webserver"?

Whilst the article rightly mentions aioquic to use HTTP/3 with Python, it is only a minimal example server. Hypercorn is a compete ASGI server built on aioquic that is likely more useful practically.