WebGL Without a GPU
microlink.ioChrome doesn't render WebGL. ANGLE does.
Why the gap is 4×. The change: One line.
The catch: You need a display
Why Mesa is built from source. Proving it.
That report is also the CI gate! The numbers.
Indeed, the post is rather obviously written by Claude. It's just missing a few "load-bearing"s and a "golden", so that I could have the full picture.
It's sorely missing a few figurative usages of "quietly", too. And not to forget the "honest caveats" and "smoke tests".
Why would you not use a server with webgl support if that's a requirement? I feel like the moment this would become an issue you are already at an scale that would make sense.
Our service is offered starting for free; the CPU server is much cheaper, and I wanted to see if it could be sufficient for most basic WebGL animations.
The GPU tier makes sense for paid users; that will be the next blog post!