I think that's true, but the same statistics of people on diet can be found, and I think (without any statistics of my own) that culture and group mentality plays a role there as well.
Well for the last 4 months, MSBuild alpha has been out with the option to use "dotnet migrate" to migrate a project.json to a project.csproj file.
The other 6 months I agree has left people in a limbo. Only people following the discussions closely would have an idea of which direction they were going.
You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear.
While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.
I'm working on a browser game, that does all communication to the game server through WebSockets.
Here I have the clients ping the server every 2 seconds, and if I haven't received a message with in 10 seconds (including other messages than ping) I consider the client dead.
Each socket is assigned to an individual player, and if that player opens a second connections the old one dies.
To be honest - In regards to the missed messages and order of events, I just cross my fingers and hope TCP does that for me.
In regards to the clustering, I have my map split up into sections, so most of the messages that needs to be send, are only to the people in that sector. So I rarely send a message to all players.
I'm still experimenting, so I'll probably still have a lot of edge cases that I'll have to cover. But for now it seem to work well.
https://gifs.com/player/G6m3vQ