winit

Good to see more alternatives in this space. If I can make one big app design request it would be this: Don’t assume that apps can always create their own windows. This has been a snag for winit and several others. Allow creating a GUI given an existing window handle. See e.g. https://github.com/rust-windowing/winit/issues/159 If you create a rust ui framework that supports the VST windowing/event loop model and just supports one GUI backend on Win32/MacOS, then many people in the audio plugin community would be very happy.

As I mention in the post, users of glutin should update their application to use the new glutin release candidate. Back ports are a PITA, and I'd hate to have to do one. I should also mention, I'm the current maintainer of glutin. Feel free to ask me any questions, or join us at our chat: https://crates.io/crates/glutin Here's our crate io, too, fwiw: https://crates.io/crates/glutin Please also consider taking a stab at some of the tasks in our and/or winit's bug tracker. I'm grateful for every bit of help. https://github.com/tomaka/glutin/issues https://github.com/tomaka/winit/issues

Browsers do a lot of blacklisting of drivers with known problems. Things are slowly improving, especially as browsers themselves, especially Firefox, steadily do more GPU stuff (putting pressure on the driver makers to fix things), but there’s a reason why it’s been very rare for non-game UIs to target GPUs for rendering: GPU drivers are atrocious. Even if they don’t crash, the number of absolutely fundamental and critical bugs that they have is very impressive. As an example of a fundamental thing being broken, try https://github.com/tomaka/winit/pull/332#issuecomment-341383... and later on down in the thread where a driver update fixed it.