News for hackers. Stuff that matters.
Re:Porting the Unity Engine to .NET CoreCLR by pcwalton on Tuesday April 10, 2018 @06:16PM (#16806054)
I hope they don't use naive reference counting. It would reduce throughput and would not eliminate pauses. A standard incremental or concurrent generational tracing GC would be a better choice. In games you have a lot of knowledge about timing that you can use to help schedule GC: you always know (or should know anyway) how much time there is until the next VBLANK, so you can use that to bound pause times for your major collections.
Re:Porting the Unity Engine to .NET CoreCLR by doomlaser on Friday April 13, 2018 @10:19AM (#16830217)
Large parts of iOS and its ecosystem use automatic reference counting, and it has a reputation for the interface being noticeably smoother than Android, which uses Java's garbage collector.
Re:Porting the Unity Engine to .NET CoreCLR by pcwalton on Sunday April 15, 2018 @07:17PM (#16845594)
Android doesn't use the HotSpot garbage collector.