The next fight was to move from C and C++ to Java and C++. This still hasn't happened in console gaming because the overhead needed for gc is not palatable to aaa developers that have to milk every byte of ram in the machine.
Regarding GC and consoles, how do the UE 4 developers approach it, just disable the GC related features then?
The UE4 GC is purpose built, simple (mark and sweep), and limited to only certain objects/allocations. The only time I've seen significant GC times/hitches was related to a bug that resulted in thousands of small allocations every second. I would much prefer if Epic dropped the GC - losing tight control over object lifetimes is as bad or worse than any potential performance overhead issues in my experience - but failing that I don't think its inclusion is a serious concern for shipping on consoles.
Yes, there is a lot of of C++ under the hood in Unity, but I also remember the days when writing game engines in C and Pascal dialects actually the majority of the code looked something like:
Yet 30 years later we seem to have forgotten how bad those compilers were targeting home computers and how much they have improved in all these years.We need more success stories like Unity to keep driving the industry forward.