News for hackers. Stuff that matters.
Re:Show HN: Strife, a 2D game library for Go by robmaister on Saturday September 29, 2018 @12:45PM (#18101318)
Once you get past a certain point of developing a complex game in Unity, one of the optimization techniques is to keep runtime allocations at 0 bytes in order to prevent a GC pause from ever happening. This was a huge pain back when Unity was on Mono 2.10.8 (released Dec 2011) but it's a bit better now.

It's a fight against the GC typically

Re:Show HN: Strife, a 2D game library for Go by coldtea on Saturday September 29, 2018 @01:28PM (#18101599)
>Once you get past a certain point of developing a complex game in Unity, one of the optimization techniques is to keep runtime allocations at 0 bytes in order to prevent a GC pause from ever happening.

It is, but it's still an option. It's not like "language with GC" == no-go for games, as the parent implied.

Re:Show HN: Strife, a 2D game library for Go by kjeetgill on Saturday September 29, 2018 @12:55PM (#18101399)
Unfamiliar with any game codebases or much C++, but I know in C we'd do zero-allocation or controlled arena allocation for "embedded" uses. I'd imagine Allocation tuning is always present. Was it much harder in C#?
Re:Show HN: Strife, a 2D game library for Go by pjmlp on Saturday September 29, 2018 @02:25PM (#18101926)
.NET has support for stack allocation and manual management of native memory.

Many forget that MSIL is rich enough to support C++, initially via Managed C++, later replaced by C++/CLI.

The major features in C# 7.3 are related to slices, improved stack allocation and reducing copies of value types.

Re:Show HN: Strife, a 2D game library for Go by pjmlp on Saturday September 29, 2018 @02:20PM (#18101913)
Just like it is a fight against malloc() if the game's architecture is not done properly.