submitted 2 years ago* (last edited 2 years ago) by to c/linux@lemmy.ml
 

Zed is a modern open-source code editor, built from the ground up in Rust with a GPU-accelerated renderer.

you are viewing a single comment's thread
view the rest of the comments
[–] 29 points 2 years ago (25 children)

I still don't understand why I should need GPU acceleration for my fucking TEXT EDITOR

  • source
  • hideshow 25 child comments
  • [+] 51 points 2 years ago* (last edited 2 years ago) (5 children)
  • [–] 3 points 2 years ago (4 children)

    Shouldn't the DE/Window Manager be handling that? Seems like doing it on a window by window basis would be inefficient (and look inconsistent).

  • source
  • parent
  • hideshow 4 child comments
  • [–] 21 points 2 years ago (2 children)

    That’s a totally unrelated part of the stack. These days you just have a compositor that combines the output of applications.

    The model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years ago (1 child)

    The model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.

    Thats where we get into explicit and implicit sync right?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 38 points 2 years ago (9 children)

    Same reason you need it for your terminal (see kitty terminal). It's surprisingly slow to cpu render text, gpu rendering is more power efficient and far more responsive

  • source
  • parent
  • hideshow 9 child comments
  • [–] 18 points 2 years ago (3 children)

    It was surprising how gpu accelerated rendering helped read logs better. Niche case, but better was better.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 years ago (2 children)
  • [–] 5 points 2 years ago (3 children)

    Surprisingly slow compared to GPU rendering. But... is it really "surprisingly slow"? If it was some 10mhz machine, then sure... I'd agree with you.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 2 years ago (2 children)
  • [–] 4 points 2 years ago (1 child)

    Maybe I'm missing something, but shouldn't the benchmark be a good approximation to the real workload? I don't see how the measurements reflect the performance difference in real life usages.

    Why would I need 100MiB/s processing as opposed to 20MiB/s processing, when I can only read maybe several lines per second?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 16 points 2 years ago (5 children)

    I mean, it should be clear. Smooth and fast and snappy. If you don't want that, use neovim like me :)

  • source
  • parent
  • hideshow 5 child comments
  • [+] 4 points 2 years ago* (last edited 1 year ago) (4 children)