26 ms·
> Code that works 100% of the time is better than higher performant code that explodes in your face every once in a while. That depends. In game programming, i
by golergka 11y ago
> Code that works 100% of the time is better than higher performant code that explodes in your face every once in a while.
That depends. In game programming, if I had a choice between a render that will crash once every 10 hours and produce 60 fps (in some model envrionment) vs a render that never crashes but produces 45 fps, I would choose the first one.
- iofj 11y agoDitto for math libraries, machine learning libraries + tools, statistics calculations and matrix multiplier kernels. Hell, I'd take a 1% chance of blowup for a 10% speedup any day.
- pif 11y ago> I'd take a 1% chance of blowup for a 10% speedup any day. Are you serious? Would you base your research career on software that you don't trust? I wouldn't. Please, notice that 1% chance of full blowup means a not-null probability of nice-looking-but-actually-false results from time to time, and that's a risk no researcher is allowed to accept.
- iofj 11y ago> Are you serious? Would you base your research career on software that you don't trust? I wouldn't. I guess you haven't seen the quality of academic code recently. The choices are basing your credibility on slow badly written code or fast badly written code.
- 0x07c0 11y agoThat is what we have fast math for :)