2 ms·
Unfortunately this kind of stuff will eventually kill C# adoption in gaming. With Unreal on one side, and Godot on the other, where while C# is supported, it i
by pjmlp 1y ago
Unfortunately this kind of stuff will eventually kill C# adoption in gaming.
With Unreal on one side, and Godot on the other, where while C# is supported, it is mostly for Unity refugees, there are very few other options left.
Yes there are MonoGame, FNA, Stride and so on, but they lack the same kind of mindshare across the industry.
- TremendousJudge 1y agoWhy do you see C# adoption in gaming as desirable? Honest question. I think it's a good enough language, but why would it be a good fit specifically for building games?
- jasperry 1y agoI'm not the parent poster, but to me it's not about C# in particular, but that there is basically no other well-supported gamedev framework in a language that's 1) statically typed, 2) garbage-collected for safety and productivity, 3) has decent performance, and 4) has good tooling/IDEs. JavaScript, C++, and Python/GDScript are all missing at least one of those. Java could possibly fill the gap, but it's still clunkier to program in than C#, and no Java game framework has much traction. I'd be ecstatic if there were something checking those boxes that wasn't owned by Microsoft.
- pjmlp 1y agoI replied on a sibling thread. However I would point out that before Unity took off, jMonkeyEngine had a good following. And since reference counting is also garbage collection from CS point of view, I would add Swift with the game development kits, however that is pretty much Apple only, thus not really the same league. Microsoft unfortunately since XNA, the whole DirectX team has been anti .NET, they didn't even provided Windows Runtime Components for .NET Native, even though it would have been relatively easy to do so, as it is based on COM (plus some extras). The moment key people responsible for XNA left the building, it was done. https://youtu.be/wJY8RhPHmUQ?si=QvtVZHhB6ZhT95eT https://youtu.be/wJY8RhPHmUQ?si=QvtVZHhB6ZhT95eT
- jasperry 1y agojMonkeyEngine is on my list of things I want to do a project in. I hope it continues to get support. It might be better for 3D than Godot (based on hearsay anyway)
- pjmlp 1y agoBecause I am firm believer in managed languages, and while I am also big into C++, I would like to still see the Xerox computing vision become reality on my lifetime. Game developers usually are the last ones to move, and tend to do so due to external factors, mostly pressed by platform owners. It was like that when we moved from Assembly in 8 and 16 bit platforms, slowly into Object Pascal (Mac/PC) and C. Then it took until Watcom C/C++ on PC, and PlayStation 2 SDK, for C++ to finally start being taken seriously by game devs, then XBox did the rest on console space. C# had a first victory in 2004 with Arena Wars, in OpenGL https://en.m.wikipedia.org/wiki/Arena_Wars https://en.m.wikipedia.org/wiki/Arena_Wars Managed DirectX was already around, then XNA on XBox Live Arcade was the needed push. When Microsoft killed in name of C++ and replaced it with DirectX TK, as usual in Windows in their territorial attitude, Mono project came up with MonoGame as rescue. This is what enabled them to eventually join efforts with Unity, when they were rewriting the engine to be cross platform, and go beyond OS X. Eventually Unity alongside C#, use to have a certain Flash like vibe, and for many, the entrypoint into the .NET ecosystem. So it is kind of sad see this go away. I don't believe in the one true language for everything, other than Timex BASIC, the moment I learned Z80, I have been a polyglot ever since. A cool designed game, even in PyGame, has probably more entertainment value, than yet another remake in Unreal running on a PlayStation 5 Pro.
- xandrius 1y agoTyped, great std lib, managed memory, one of the most usable languages, C-like and fast. It's such a pleasure to write in C# and you know that you won't get dumb ninja issues because of pointers or types.
- Rohansi 1y agoI disagree. I believe there are enough game developers out there who enjoy using C# that would look for it in their next game engine. If Unity is gone it would leave a large hole to fill. The upside is Unity's C# support is the worst available in any game engine. It's stuck on an old C#/.NET version, .NET (Core) runs C# code 2-5x faster than Mono (and IL2CPP) [1], and its garbage collector is slower than the one Mono ships with (which is also slower than .NET). [1] https://xoofx.github.io/blog/2018/04/06/porting-unity-to-coreclr/#performance-with-coreclr https://xoofx.github.io/blog/2018/04/06/porting-unity-to-cor...
- pjmlp 1y agoI have been long enough around, not to be as hopeful, however I loved being proven wrong on this one. Note that Native AOT doesn't do consoles, and Godot can't target them with C#, it is also why they've problems with targeting Web. Also Native AOT, and proper C# still lack some of Burst (HPC#) capabilities.
- Rohansi 1y agoYes, consoles, phones, and web are the hard ones to support due to a lack of JIT support. That's going to take some time to resolve. Especially since Native AOT is much more restrictive than IL2CPP. IMO Burst was a mistake. C# running under .NET runs significantly faster without needing to write code differently. And if you need to go even faster you can write code differently to make use of modern C# features to boost performance rather than relying on a secondary compiler that only allows a subset of C#.
- pjmlp 1y agoOn the contrary, I was there when game devs took some convincing that C / Object Pascal compilers were getting good enough over Assembly, even if some inline Assembly was still required in hot paths. When the whole C vs C++ quality of code generation debates started, that were the genesis for Matt Goldbolt while still working at the games industry, to have created Compiler Explorer as means to shutdown discussions regarding C++'s adoption, which nonethless persist to this day, especially in the Handmade community. Burst was necessary, to have industry legends like Mike Acton come and join Unity, despite their strong opinions against C++.