Support Silk.NET

Summary
We propose adding support for Silk.NET in Stride 3D to enhance the framework's flexibility, modernize its API ecosystem, and empower developers with a high-performance, cross-platform abstraction for graphics, compute, and input handling.

Motivation

• Cross-Platform Consistency: Silk.NET provides a unified API that simplifies cross-platform development, aligning with Stride 3D's goals of delivering a seamless multi-platform engine experience.
• Performance Optimization: With low-level access to modern APIs like Vulkan, OpenGL, and DirectX, Silk.NET offers potential performance improvements and compatibility across a wider range of devices.
• Ease of Adoption: Silk.NET is actively maintained and well-documented, enabling developers to leverage the latest technologies in their Stride 3D projects more efficiently.
• Community Collaboration: Integration with Silk.NET can attract contributors and developers familiar with the library, fostering collaboration and innovation within both communities.
• Future-Proofing: As a modern library, Silk.NET ensures compatibility with current and emerging hardware and APIs, keeping Stride 3D relevant in the evolving graphics development landscape.

Benefits
This integration will:

• Improve Stride 3D's flexibility and compatibility with modern APIs.
• Enhance performance and efficiency for developers targeting multiple platforms.
• Expand Stride 3D's appeal to the wider developer community.

By supporting Silk.NET, we take a step forward in empowering developers and ensuring Stride 3D remains a competitive and modern engine for game and 3D application development.

Funding
When developers are interested they can request support in the form funding. We have allocated a project for this on Stride's open collective.
https://opencollective.com/stride3d/projects/stride3d-silknet

References

• Silk.NET Repository
• Silk.NET Documentation

The issue names no Stride files, tests, or entry points. Start by reviewing the Silk.NET repository and documentation linked in the issue, then identify the Stride subsystems and supported graphics or input APIs that an integration would need to cover. Done criteria are not defined, so the integration scope and acceptance tests would need to be agreed first.