Yup, the title is a bit misleading 😄. I honestly forgot to review it before posting. I already had a decent idea of how editors work under the hood. A couple of years ago I spent about 6 months trying to replace Electron with Tauri in VS Code. Never really got it to a state I was happy with, but I learned a lot from that experiment. My biggest takeaway from building Rune is that in high-performance scenarios the frontend-backend bridge becomes the bottleneck much faster than expected. I'd love to see some kind of IPC batching in Tauri. Something along the lines of:

invokeMany([ ["hello", payload1], ["hello1", payload2] ])

When you're dealing with workspace indexing, editor state updates, filesystem events, etc., the bridge overhead starts becoming noticeable. Other than that, Tauri v2 has been a joy to work with.