Vulkan Cleanup

[ShipmasterKyle]

A big goal of libfinite is encouraging devs to use Vulkan instead of OpenGL. We support OpenGL in order to make sure that the compositor can work without a custom backend as well as making the porting process easier, but our standard always points towards using Vulkan.

That said, the Vulkan api in the library is very unsafe for large scale use. The Vulkan Memory Allocator should be implemented into the libfinite api to ensure it's safety for high volume usage.

[nexocreamery]

A big goal of libfinite is encouraging devs to use Vulkan instead of OpenGL. We support OpenGL in order to make sure that the compositor can work without a custom backend as well as making the porting process easier, but our standard always points towards using Vulkan.

That said, the Vulkan api in the library is very unsafe for large scale use. The Vulkan Memory Allocator should be implemented into the libfinite api to ensure it's safety for high volume usage.

why dont you work on it, and if not what are you working on?

[ShipmasterKyle]

The issue with implementing the VMA is not about not wanting it, in fact it's actually a high priority issue. The problem is that we as a team have a lot of ground to cover in not a lot of time so we'd like to get the base implementations in (things like basic window rendering features, audio, player API) first and then address polish and performance issues after.

In otherwords we're focused on being comprehensive in our base of the API so that once the basics are in, we can always add enchancements like VMA later.

Right now, addressing the security concerns in the input API is our biggest concern going into v0.8.0 as I mentioned in #12