6 ms·

In this case wgpu is just providing the surface texture for the window that the software rendered pixels are drawn into.

• deleted 2mo ago
  [deleted]
• john01dav 2mo ago
  Softbuffer? (I originally wrote this a few years ago but other people maintain it now)
  • LoganDark 2mo ago
    I like softbuffer, but it owns its window and doesn't support as many events / integrations as winit.
    • soxfox42 2mo ago
      You might be confusing softbuffer for minifb here, as softbuffer doesn't do any window handling of its own. All window management and event handling happens through winit (or another crate providing a HasWindowHandle implementation).
      • LoganDark 2mo ago
        Oh, you're right! My bad
• articulatepang 2mo ago
  Yes, exactly this -- it's a fast and convenient way for my code to just write the pixels into a spot in RAM (the CPU's RAM, not VRAM) and have those pixels end up on screen. On modern architectures this nearly always goes through a GPU, so even if you're not using the GPU to accelerate your 3D rendering/math, you gotta deal with it just to put pixels on a screen at the end of the day. So that's what wgpu does for me.