Hi again, and thanks for a really nice looking library!

I was wondering if you have considered using (or adding) glow as the OpenGL backend in three-d?

Some direct benefits:

• No need for build.rs (I tend to shy away from libraries using it).
• No need to build and maintain the cross-platform OpenGL bindings yourself (though I guess most of that work is already behind you).
• You can use egui_glow instead of rolling your own.

The reason I ask is for egotistical reasons. I would love to be able to write an eframe app and then add a high-level 3D rendering library on top of it. And three-d looks like it could be a great candidate for such a library! In such a world eframe could focus on being a good framework for setting up a window, and three-d could focus on being a great 3D rendering library.

Of course we could instead build out the framework part of three-d to be as feature-complete as eframe, but that's a lot of work (for instance: eframe has a bunch of code in it to handle mobile text input on the web), and it would greatly detract from what three-d is: a 3D rendering crate.

There are likely subtleties here that I'm not seeing, but I thought I would at least throw out the idea!

I guess another way to phrase this issue is: do you think three-d could be made into a library, built on top of glow?

PS: even though I am the author of eframe I would love to throw it away if there was a good alternative.