Migrating away from Rust (deadmoney.gg)

Article summary

The article discusses the author's decision to migrate their game development project from Rust and the Bevy game engine to C# and Unity. The author cites challenges with collaboration, abstraction, and migration as reasons for the switch. Despite enjoying working with Rust, the author found that Unity and C# better met the project's needs for accessible collaboration, rapid gameplay iteration, and a stable ecosystem. The switch resulted in improved development speed and a more maintainable codebase.

Main themes

• Game development
• Programming languages
• Engine choice
• Collaboration and accessibility
• Security and licensing
• Ecosystem and community
• Performance and optimization

What commenters say

• C# is a highly underrated language that has become more terse and efficient over time, making it a good choice for game development.
• The use of external libraries can greatly reduce the amount of code needed, making C# a more practical choice than Rust for some projects.
• The .NET platform's inclusion of many libraries and tools can make it easier to develop secure software, but some argue that this can also lead to dependence on Microsoft.
• The choice of programming language and platform depends on the specific needs and constraints of the project, and there is no one-size-fits-all solution.
• Some developers prefer C# and Unity due to their ease of use and large community, while others prefer Rust and Bevy for their performance and flexibility.
• The importance of security and licensing considerations can vary depending on the industry and region, with some sectors preferring open-source solutions like Java.
• The transition to AOT compilation is seen as a key factor in the adoption of C# and .NET, but some argue that it is not a priority for all use cases.