4 ms·
I think Rust would eat into C++ more than C#. Microsoft is pushing C# and the tooling fairly hard right now. Performance is pretty good and even though Rust s
by jayd16 6y ago
I think Rust would eat into C++ more than C#. Microsoft is pushing C# and the tooling fairly hard right now.
Performance is pretty good and even though Rust seems like a rising star, it won't reach C# levels of tooling for quite some time.
I don't think the population of studios that chose C#'s performance and convenience over C++ but would now choose Rust is all that large.
But hey, lets start talking about bindings. We could be changing all these C#/C++ engines into C#/Rust engines.
- suprfnk 6y ago> even though Rust seems like a rising star, it won't reach C# levels of tooling for quite some time. Just curious; what's the tooling gap between Rust and C#, according to you? I work in C# profesionally, and dabble in Rust, and haven't really found Rust tooling lacking yet -- but maybe that's because I'm only working on small hobby projects.
- pjmlp 6y agoTry to do something like WinUI in Rust, or debug a mixed code base like in C# and C++ on Studio.
- lostmsu 6y agoAren't you using refactoring tools like ReSharper? Also, what about debugging? C# does edit & continue and allows arbitrary statement execution during debugging. Does Rust debugger even allow moving the instruction pointer at will?
- Iwan-Zotow 6y agoNot in a game business, but I could tell you - until Rust is supported (down to debugging) in Visual Studio, there would be no C#/Rust apps, and plenty C#/C++ apps.
- halvnykterist 6y agoDebugging in VS actually works pretty well already, the msvc target generates PDB files. It's what I use when need to attach a debugger to something. Actual language support would be really nice, though. Hopefully MS are already working on this.