How do you render billions of vertices and maintain a gameplay loop under 8ms for AAA games without precise manual memory/layout management?
Not everyone is writing websites in javascript
How do you render billions of vertices and maintain a gameplay loop under 8ms for AAA games without precise manual memory/layout management?
Not everyone is writing websites in javascript
https://people.inf.ethz.ch/wirth/ProjectOberon/Sources/Kerne...
For something more modern in D, also a GC enabled systems programming language,
So i don't know what point you are trying to make
D is pragmatic and confirms my point
Modula-2+, Modula-3, Nim, Mesa/Cedar, .NET Native, Sing#, Oberon, Oberon-2, Oberon-07, Active Oberon, Nim, Swift (RC is a GC algorithm per CS definition), and even if debatable what its role might be, Go.
The point I am making is having a GC managed heap doesn't preclude features for manual memory management, only GC haters think otherwise.
Some helpful reading, from people actually working on solving hard problems
https://twitter.com/FilmicWorlds/status/1562090212225716224
> only GC haters think otherwise.
only GC lovers think like that
that's not a good argument
You still don't get GC enabled system programming languages, and apparently I am not the one that is going to make it clear, so whatever.
Odin is 100x better environment to program in than C. C++ is used for AAA games. Rust is not really used if hardly at all because of the highly competitive and time critical nature and very much the need to change things fast.