kettle11
commented
3 years ago Good question!
kapp aims to:
- Build as quick as reasonably possible (it clean builds in 1/4th the time of
winit) - Correctly implement little, often neglected, details like:
- Smooth window resizing
- Monitor color spaces
- Be very simple architecturally
It's not (yet) trying to be as robust and cross-platform as winit, but it's also not as focused and simple as miniquad, which is tightly coupled to GL. kapp is a middleground between the two.
If you compare the three today kapp is less mature. kapp has clearly missing features and numerous small bugs. kapp also doesn't support Linux yet, which is important to much of the Rust community. Sometime next year, when kapp is a little further along, I plan to release an initial version on crates.io.
What does kapp do differently than alternatives like winit or (probably the most similar) miniquad?