Quote:

you may think of UDP as of an analog of good old C: you can do pretty much everything, but it is not because the language helps you – it is rather because it doesn’t stand in the way :-)

Another Quote:

As most of the routers (including pretty much every backbone router out there) are not configured to support multicast, it makes multicast over the public Internet hopeless :-(

Quote:

Doing sanitization at IDL level automates quite a bit of tedious-and-error-prone work, which is always a Good Thing™

Another Quote:

Hey, this whole thing can be made MUCH simpler, the only thing we need to acknowledge is that the best identifier for a string is the string itself!

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

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