Zed editor switching graphics lib from blade to wgpu

Re:Zed editor switching graphics lib from blade to wgpu by socalgal2 on Friday February 13, 2026 @09:16PM (#47010842)

hard is this: https://faultlore.com/blah/text-hates-you/

and this: https://lord.io/text-editing-hates-you-too/

those are both things most ImGUIs ignore. And, even if you pick some library that somehow handles the first you're left with all of the issue mentioned above.

To be clear, if I was writing a devtool (and I am actually) i'd reach for an ImGUI (and I did). But I'd be unlikely to use one for user facing tool.

[ Parent | on HN ]

Re:Zed editor switching graphics lib from blade to wgpu by jason_oster on Saturday February 14, 2026 @01:17AM (#47012092)

Those are also things that most retained mode GUIs ignore, unless they are "platform native". Only a small number of GUI implementations get these things right because they are hard. There are many, many GUI implementations, and most of them are pretty rough, to put it mildly.

It has nothing to do with how the state is managed. (This is the only distinction between immediate and retained modes.)

[ Parent | on HN ]

Re:Zed editor switching graphics lib from blade to wgpu by piker on Saturday February 14, 2026 @05:48AM (#47013469)

Tritium is a rich text editor. I'm familiar with the issues outlined in those posts.

To be fair with a lot of the GUI frameworks in various ecosystems ... they try to solve different pieces of them.

[ Parent | on HN ]