3 ms·
Wasn't to discourage at all--was trying to give my understanding (based on the design docs, talks, etc.) of what your CPU budget looks like and speculate about
by twotwotwo 11y ago
Wasn't to discourage at all--was trying to give my understanding (based on the design docs, talks, etc.) of what your CPU budget looks like and speculate about ways to deal.
"It'd be really cool" was absolutely sincere; the Go folks have given us some new toys and it'd be neat to see how far we can take 'em.
- pjmlp 11y agoThat was my point as well. The culture in the gamedev world is such that the big teams only switch tooling when forced to do so. Only amateurs tend to try out new ways. Back when the move from Assembly to higher level languages started, many games would be filled with inline Assembly. The compilers weren't that good generating code and they didn't want to loose the power of Assembly. Just like now with the managed runtimes and having tons of C and C++ underneath. Languages that weren't that speedy 30 years ago. We need to keep the spirit of taking things far alive, because in computing seeing is believing.