“No Bugs” Bunny
Avoiding Ugly Afterthoughts. Part a. From Writing for Cross-Platform, to Writing for Debugging and Production Post-Mortem, with Error Handling in between
March 28, 2016 by • “No Bugs” Bunny
Quote:
It is strongly recommended to have your build server to compile your game for at least two sufficiently-different platforms from the very beginning
Another Quote:
If allocation of 50 bytes causes an “out of memory” error, we’re probably already long dead because of unacceptable swapping. And even if we disabled swap file – chances that we will recover from this condition, are infinitesimally small
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System Architecture(Re)ActorsOn.ProgrammingDebugging
Read moreOnce Again on TCP vs UDP
March 21, 2016 by • “No Bugs” Bunny
Abstract:
The choice of TCP over UDP (or vice versa) might not always be obvious. In a sense, replacing TCP with UDP is trading off reliability for interactivity.
Quote:
The most critical factor in selection of TCP over UDP or vice versa is usually related to acceptable delays
Filed under: On.ProgrammingNetwork Programming
Read moreOn Zero-Side-Effect Interactive Programming, Actors, and FSMs
March 14, 2016 by • “No Bugs” Bunny
Abstract:
“WHY are functional programming languages not popular for interactive programming purposes?" and "WHAT we can do about it?"
Quote:
IMNSHO, deterministic Actors are the very best thing in existence for interactive programming, with lots of very practical benefits (from production post-mortem, to protection of in-memory state against server faults).
Filed under: On.System Architecture(Re)Actors
Read morePassword Hashing: Why and How
March 7, 2016 by • “No Bugs” Bunny
Abstract:
Password hashing is a Big Headache, and doing it right is complicated
Quote:
Note that none of the C++11 random number engines (LCG, Mersenne-Twister, or Lagged Fibonacci) can be considered good enough for cryptographic purposes – in short, they’re way too predictable and can be broken by a determined attacker, given enough output has leaked.
Filed under: On.SecurityBest Practices
Read more





