tydok

Ask more? The book is expensive. If he lowers the price, say to $10, the sales will probably increase 10x.

> How far should we go in making things generic ?

Never make things generic apriori.

Yeah, but perhaps the 90% of each 5% is common to all users.

Exactly. It scales linearly, not quadratically. I forgot to mention that since clients do the "original" encoding, the server actually does less work (regarding resolution tiers).

> 100 outgoing video feeds. Not many machines can encode 100 video feeds in realtime

The server will send 9 video streams to each connection, but it has to process only 10 video streams since it will send the same video data to all clients, if we ignore client bandwidth.

Still, isn't it one stream per client? Why 10 streams each?

Firstly, a client will have 10 outgoing video streams at most, not 100!

Secondly, if we consider receivers bandwidth, a client can encode 2 or 3 video streams, e.g. low, medium, and high quality video.

The fundamentals are about positional elements and strategic principles.

For example: Relative value of the pieces, Control of the center, Pawn structure, Tactics, Initiative, Tempo, Opposition, Keep the position balanced, Develop multiple ideas/areas (strategy), Control open lines (files/ranks/diagonals) and crossings

Yes, it's indeed a property, not a problem. The problem is the accidental complexity which has the tendency to increase and requires constant effort/energy from us to keep it low.

"I have yet to see an interesting piece of code that comes from these OO people [...] It claims that everything is an object. Even if it is true it is not very interesting"

We use double buffering to avoid flickering, but still we have to clear the back buffers.

Classes vs Data Structures, or maybe Objects vs Data Structures, or maybe Classes vs Objects, or maybe Data vs Data Structures, or maybe Data vs State, or maybe Classes vs Types, or maybe OOP vs FP, or maybe I don't know what I'm talking about...