A lot of countries require you to declare your total wealth on your tax forms. Then once someone gets audited, that gets checked. Obviously it’s possible to hide it, but that in itself is a crime, and not everyone is willing to risk going to jail over paying taxes.
I’ve always felt they weren’t really worth it for performance per dollar spent. For C++ work I just use a non-Mac workstation. For lighter workloads the Mac Mini is very capable already.
If you add multiple IPs to a record, a lot of resolvers will simply use the first one. So even in that case you need a low TTL to shuffle them constantly
Client-server multiplayer games are already kind of a very specialized type of video playback if you squint a bit (you're transmitting entities rather than pixels).
This method of multiplayer you propose is inferior in basically every way: you can't do client-side prediction to make inputs feel smoother, and non-trivial scenes will surely take up more bandwidth than just transmitting entity deltas.
Agreed. I feel that a lookup table can probably map all emojis possible to a uint32 (maybe optimistically uint16, [1] says there's about 4k emojis, does that include skin variations?). And you can add new ones sequentially after so IDs remain stable.
The fix is setting canvas width to window.innerWidth * window.devicePixelRatio, and height to window.innerHeight * window.devicePixelRatio. Then use CSS to maximize the canvas on the screen.