Oddbean

@reya One problem Blowater has is that it heavily uses IndexedDB which is slow and has horrible APIs. As much as I can optimize it, it’s a bad foundation to be built on. I believe your investment in native desktop technology is very worth it in the long run. Web is very good at presenting / displaying things but very bad at everything else. Tauri is a good approach. We can use Rust to implement a performant storage layer. I look forward to see what you make with Coop

I'm working to few improments, and release a stable version for Coop in this weekend. My initial plan is use Native GUI instead of Tauri (webview), but I came back to tauri because my rust skill isn't enough to do it 😅. My only problem with tauri is it heavily depend on gtk3 on linux which quite old, and I found some native features like context menu, tray,... isn't work well on wayland. It also doesn't provide much API for custom window like macos or windows. In the long term, I want to do everything in Rust, so I can have more control in the quality without depend on 3rd libs. my target stack: - backend: rust-nostr - db: nostrdb or sqlite - gui: gpui or xilem, florem

hmm, I not use egui much yet to review it, but egui is more mature than gpui, and well supported too. My only problem with egui is it hard to create native looking app (it not egui goal anyway 😅)

I like egui a lot. It’s very simple conceptually: at any point you can ask how much room is available to render in, and you can draw anything immediately at that point, relative to that point, or absolutely anywhere. The layout system maintains a cursor of where it’s currently drawing, and moves left to right, up down, etc depending on the layout you’re using. That’s all there is to it really. Using this I have been able to build some powerful controls. The one that impressed me the most about egui was egui-nav, where I built an entire ios-style navigation control without too much effort.