News for hackers. Stuff that matters.
Re:Xenko Game Engine 2.0 released by emsy on Tuesday April 25, 2017 @06:19PM (#14198656)
Unity games are often reported to have performance issues, allegedly due to the underlying GC (or lack of understanding of it). I'd rather hope for the adoption of a less messy C++ alternative that is suitable for quasi-realtime applications. So far Jai seems to be the most serious competitor in this regard.
Re:Xenko Game Engine 2.0 released by pjmlp on Tuesday April 25, 2017 @06:26PM (#14198709)
Because Unity uses a Jurassic Mono implementation with a stone age GC and JIT implementation.

By the same metrics, we should evaluate performance of C and C++ code by using benchmarks with MS-DOS C and C++ compilers, which should be about the same age.

Don't mix languages with implementation when talking about performance.

Re:Xenko Game Engine 2.0 released by socialist_coder on Tuesday April 25, 2017 @09:51PM (#14199891)
Amen brother. I think most perf problems in Unity games would go away if Unity updated their GC. It's definitely our #1 source of frame rate hiccups. Plus, it makes you write weird crappy code just to avoid GC allocations. Ugg =(
Re:Xenko Game Engine 2.0 released by Yuioup on Wednesday April 26, 2017 @01:39AM (#14200686)
Are there plans to replace Mono with .NET Core?
Re:Xenko Game Engine 2.0 released by pjmlp on Wednesday April 26, 2017 @03:08AM (#14201053)
No, Unity guys are doing their own thing with IL2CPP.

Basically they generate C++ from MSIL as a means to generate native code, instead of building their own compiler backend.

They plan however, to eventually update their Mono runtime.

https://forum.unity3d.com/threads/future-plans-for-the-mono-...

Re:Xenko Game Engine 2.0 released by AlexeyBrin on Tuesday April 25, 2017 @08:52PM (#14199636)
> So far Jai seems to be the most serious competitor in this regard.

1. Jai is not even released.

2. Jai is a programming language, not a game engine.

Unity is slow because they are using an outdated C# implementation (some old Mono).

Re:Xenko Game Engine 2.0 released by emsy on Wednesday April 26, 2017 @03:02AM (#14201034)
1. If you follow its development you know the features and the design philosophy. What's your point? 2. I picked Unity because it's the most popular engine with an underlying GC.

Regardless of their GC implementation, in games you don't want opaque runtime behaviour, which a GC always introduces. This leads to weird workarounds in your code that nobody understands instead of having clear and explicit memory management.

Re:Xenko Game Engine 2.0 released by AlexeyBrin on Wednesday April 26, 2017 @03:57AM (#14201254)
My point is that until a language is proven, as in used on a large scale it is just a nice idea. Let's wait until Jai is released and used by different teams for different tasks until we proclaim its superiority.
Re:Xenko Game Engine 2.0 released by emsy on Wednesday April 26, 2017 @04:48AM (#14201489)
I didn't claim superiority, I just that it's the most serious competitor. A point I still stand by. The original post compared the adoption of C# to the adoption of C++, the now de-facto standard for games. C# does not have what it takes to become the de-facto standard for games.
Re:Xenko Game Engine 2.0 released by pjmlp on Wednesday April 26, 2017 @05:10AM (#14201583)
Sure it does.

C++ became a de-facto standard for games, because console SDKs moved from C to C++, pushed by the companies selling them.

The same companies that are now adopting Unity and have already toyed with the idea of having a C# SDK.

If for the sake of example, PS5 SDK would be C# based, devs that wanted any money from PS5 games would adopt it, regardless of their feelings regarding C++ vs C#.

Re:Xenko Game Engine 2.0 released by emsy on Wednesday April 26, 2017 @05:37AM (#14201706)
>If for the sake of example

This is a terrible example and you have no idea what you're talking about.

Re:Xenko Game Engine 2.0 released by pjmlp on Wednesday April 26, 2017 @05:50AM (#14201757)
As someone that once upon a time was at SCEE SOHO office, maybe I do know one or two things.
Re:Xenko Game Engine 2.0 released by adamrezich on Wednesday April 26, 2017 @05:48AM (#14201746)
Not to be too pedantic but I'm pretty sure he's never actually referred to it as "Jai" and everyone's only been inferring that because of the source file extensions.
Re:Xenko Game Engine 2.0 released by stcredzero on Tuesday April 25, 2017 @08:03PM (#14199379)
Unity games are often reported to have performance issues, allegedly due to the underlying GC (or lack of understanding of it).

Is there a way of running C# with reference counting?

Re:Xenko Game Engine 2.0 released by flukus on Tuesday April 25, 2017 @11:00PM (#14200117)
At that point you've created a different language with different semantics.
Re:Xenko Game Engine 2.0 released by stcredzero on Wednesday April 26, 2017 @01:20PM (#14205005)
I think "you can write C#, but you can only have your references form a DAG" would be acceptable in a lot of contexts, like game programming. (Existing libraries would still require some form of tracing, but I think there are ways that the tracing could be handled by another thread.)
Re:Xenko Game Engine 2.0 released by theprotocol on Wednesday April 26, 2017 @04:27AM (#14201393)
I instinctively get that thought whenever I work with C#. It's really nice but would it kill them to at least offer simplistic memory management semantics?
Re:Xenko Game Engine 2.0 released by pjmlp on Wednesday April 26, 2017 @05:06AM (#14201561)
People think RC as GC algorithm is simpler, but it isn't.

Naive implementations are slower than tracing GC, while high performance ones are as complex as tracing GC ones, while having the burden of forcing the developers to explicitly deal with cycles.

Re:Xenko Game Engine 2.0 released by stcredzero on Wednesday April 26, 2017 @01:16PM (#14204964)
high performance ones are as complex as tracing GC ones, while having the burden of forcing the developers to explicitly deal with cycles.

I bet there are plenty of game developers who would be only too glad to arrange their references as a DAG, if they could have guaranteed low latency.

Re:Xenko Game Engine 2.0 released by pjmlp on Wednesday April 26, 2017 @02:30PM (#14205660)
Maybe, but if they don't take care, some stack overflow surprises might happen, the fun of cascade deletions.