2 ms·

A good 95% of the mobile game devs I know who use Macs use Unity. Unity code is done pretty much exclusively with C#. 100% of those people use Jetbrains Rider

A good 95% of the mobile game devs I know who use Macs use Unity. Unity code is done pretty much exclusively with C#. 100% of those people use Jetbrains Rider and/or VScode. One used to use Visual Studio, but moved to Rider a good year ago. C#/.NET today is what Java wanted to be, it's an actually good and comfortable modern-ish language that actually works on multiple platforms.

MassiveBonk51 3y ago
Modern java is a fairly good language. If you don't like it, can always opt into scala, kotlin, or clojure. I don't understand what you mean by Java not working on multiple platforms. If you like c#/.net that's fine but why try to put down Java which has been cross platform for a long time?
- theshrike79 3y ago
  Cross platform is less and less important nowadays. When was the last time your phone ran a Java application natively? As in you had a legit JVM on your phone? Everything is cross-compiled or cross-translated to something else. I write C# for Unity and it translates it to something that'll run on iOS, which definitely doesn't have the CLR natively in it.
highwaylights 3y ago
The problem, and I say this being 22 years deep in it, is that .NET was never cool. That seems unimportant, but being objectively the best thing going doesn’t build a community or any word-of-mouth around your product. I’d love to think we’d see a thriving Nuget scene on the order of npm or gem, but if it was going to happen it would’ve happened by now.
- theshrike79 3y ago
  Yeah, it took a LONG time for .NET and C# to get out of the "Micro$oft Bad" -reputation. But having done a good 15 years of Enterprise Java professionally and having moved to C# for the last half decade, there isn't enough money in my country's IT salaries for me to go back to Java. It's not just the language, it's the whole ecosystem that's icky compared to C#/.NET.
  - cxr 3y ago
    Solution: cajole people from the community into effectively rebranding themselves into something sexier through a somewhat hostile fork run by competent people who "get it" and are not (currently) affiliated with MS. People love throwing support behind the rebels. Make sure to rebrand the whole thing, though. References to "C#" and ".NET" shouldn't appear anywhere except on the project's /about/history page.
pjmlp 3y ago
C#/.NET is still far away from where Java has been, in cross platform support (almost every CPU and OS has some kind of JVM implementation), and being a bit better in handling value types and going the C++ way in adding features isn't the way many of us see it as better.

MassiveBonk51 3y ago

Modern java is a fairly good language. If you don't like it, can always opt into scala, kotlin, or clojure. I don't understand what you mean by Java not working on multiple platforms. If you like c#/.net that's fine but why try to put down Java which has been cross platform for a long time?

theshrike79 3y ago
Cross platform is less and less important nowadays. When was the last time your phone ran a Java application natively? As in you had a legit JVM on your phone? Everything is cross-compiled or cross-translated to something else. I write C# for Unity and it translates it to something that'll run on iOS, which definitely doesn't have the CLR natively in it.

highwaylights 3y ago

The problem, and I say this being 22 years deep in it, is that .NET was never cool. That seems unimportant, but being objectively the best thing going doesn’t build a community or any word-of-mouth around your product. I’d love to think we’d see a thriving Nuget scene on the order of npm or gem, but if it was going to happen it would’ve happened by now.

theshrike79 3y ago
Yeah, it took a LONG time for .NET and C# to get out of the "Micro$oft Bad" -reputation. But having done a good 15 years of Enterprise Java professionally and having moved to C# for the last half decade, there isn't enough money in my country's IT salaries for me to go back to Java. It's not just the language, it's the whole ecosystem that's icky compared to C#/.NET.
- cxr 3y ago
  Solution: cajole people from the community into effectively rebranding themselves into something sexier through a somewhat hostile fork run by competent people who "get it" and are not (currently) affiliated with MS. People love throwing support behind the rebels. Make sure to rebrand the whole thing, though. References to "C#" and ".NET" shouldn't appear anywhere except on the project's /about/history page.

pjmlp 3y ago

C#/.NET is still far away from where Java has been, in cross platform support (almost every CPU and OS has some kind of JVM implementation), and being a bit better in handling value types and going the C++ way in adding features isn't the way many of us see it as better.