This is pretty much aligned with my feelings as well. I think wgpu was by far the right call. Pretty much all general purpose engines have some form of generic

This is pretty much aligned with my feelings as well. I think wgpu was by far the right call. Pretty much all general purpose engines have some form of generic "gpu device" api. wgpu solves that space quite nicely and in a more complete way than some of the other approaches in the space. It defines a default, relatively modern feature set that when targeted will work on pretty much anything. And it provides a capability detection / opt-in-feature API that allows us to expose and access other APIs we might need. It helps us embrace Bevy's core "engine features look like app features" mentality: the APIs we use to implement renderer features are the same APIs that Bevy plugin developers use to implement renderer features. More on the "Bevy App Model" philosophy: https://bevyengine.org/news/bevys-first-birthday/#the-bevy-app-model https://bevyengine.org/news/bevys-first-birthday/#the-bevy-a...