Hacker News Reader

Comment by superchroma | Hacker News Reader

"The main change for C# support is that we moved away from the Mono SDK and we now use the .NET SDK to embed the .NET runtime"

And .NET 6. Terrific work. Unity still isn't taking industry seriously so it's terrific to see viable alternatives.

View on HN

>>> Unity still isn't taking industry seriously

What does this mean?

They laid off 300 developers including some of the most experienced ones.

They are still recruiting, at least in Montréal. A friend of mine just got a SWE position there, so I think the layoffs were more due to a strategic shift away from side ventures than actually cutting from their core product.

So Google, Microsoft, etc. are taking the industry even less seriously?

I guess Microsoft and a couple of AAA studios aren't either than .

An easy example would be to look at moving to a multi csproj structure. The desire is to have business logic and unit tests in their own projects, for example. Unity forces you to have them jammed in the monolithic singular project with everything else. I don't want to ship tests to production, and I don't want to have to build everything just to run some tests, particularly automated tests done on a build server.

Unity marches on with little to no interest in enterprise development and quality processes, which is a shame.

Maybe I'm misunderstanding what you're looking to do, but you don't need to ship tests? Just use assembly definition files (asmdef)

Unity has supported multiple csproj solutions since 2017, through asmdef.

Reply on news.ycombinator.com